astexplorer
syn
astexplorer | syn | |
---|---|---|
43 | 19 | |
5,953 | 2,675 | |
- | - | |
6.0 | 9.6 | |
9 days ago | 4 days ago | |
JavaScript | Rust | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
astexplorer
-
Understanding Code Structure: A Beginner's Guide to Tree-sitter
You can play with your code here, and visualise ASTs for the same.
-
What is an Abstract Syntax Tree in Programming?
Website
-
How to create your own Eslint rule with tests, boosting the DX, and code-review
To understand this syntax, I recommend exploring AST Explorer. You will have a better view of how the AST of JavaScript works and how to correlate it with the Eslint syntaxy:
-
Programming from Top to Bottom - Parsing
You can never mistake type_declaration with an identifier, otherwise the program will not work. Aside from that constraint, you are free to name them whatever you like, there is no one standard, and each parser has it own naming conventions, unless you are planning to use something like LLVM. If you are interested, you can see examples of naming in different language parsers in the AST Explorer.
-
ESLint: under the hood
The rule that I want to write will be called not-allows-underscore: the idea is to abolish the use of underscores when declaring variables or functions. It's a real dummy rule, but it should be enough to see in action the concepts that we have discussed earlier. The first thing that I would do is to go to AST Explorer, write down a code that declares variables and functions (both standard and arrows one) and take a look at what type of node is the one that encodes the identifier. Doing that, I found out that the node type of my interest is Identifier, what a surprise! 🤣. In particular, the structure of the node holds the string used as identifier in the name property.
-
😱 ESlint over Conventions - You have Not unlocked the power of ESlint 😱
All the information about the API, AST node names, AST Explorer, etc. you can read in the official documentation. I’m just going to show examples of how to automate the check-up of our created conventions.
- AST Exploret
-
200 Web-Based, Must-Try Web Design and Development Tools
AST Viewer
-
Building a JSON Parser from scratch with JS 🤯
If you want to see how the AST of popular languages looks, I recommend the AST Explorer. It supports various languages, and you can view the complete AST and navigate through the nodes. If you want to go further, you can try to copy some logic from an existing parser and implement it in your own, such as calculating an expression according to precedence order, for example: 1 + 2 * 3 (which is 7, not 9).
-
Creating my own typescript compiler
https://astexplorer.net/ is a good resource/playground for understanding ASTs and transpilers.
syn
- 对 RTIC 框架的探索
-
Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
[2] https://github.com/dtolnay/syn/issues/782
- syn v2.0.0 released
-
How to replicate inheritance (kinda) in Rust?
It looks to me like you are trying to make a syntax tree generic over arities. I suggest you take a look at the Expr enum in syn, its variant structs, and the ast_enum_of_structs_impl macro, which is a macro that implements a trait over different Expr variants with different fields.
-
Rust AST Explorer
Rust makes this project easy by providing the syn crate (parsing and formatting) and WASM (for interactivity). Source code lives at https://github.com/CarlKCarlK/rust-ast-explorer. Contributions welcome.
- Parser for Rust Source Code
-
Rust language parsers? Do you have any recommendations?
Perhaps there should, but if you look at the commit history you'll see that syn is maintained almost entirely by dtolnay (https://github.com/dtolnay/syn/graphs/contributors). Furthermore, with Rust continually adding new syntax that needs to be supported, syn can't be easy to maintain and most of the effort probably goes into making it work at all rather than optimisations.
- Syn - Parser for rust source code
- Syn – Parser for rust source code
What are some alternatives?
deno_swc - The SWC compiler for Deno.
rust-fsm - Finite state machine framework for Rust with readable specifications
gogocode - GoGoCode is a transformer for JavaScript/Typescript/HTML based on AST but providing a more intuitive API.
explaine.rs - An interactive Rust syntax playground
vscode-language-tree - VSCode tree format support
todo_by - Compile-time lifetimes for comments.
ChakraCore - ChakraCore is an open source Javascript engine with a C API.
proc-macro-workshop - Learn to write Rust procedural macros  [Rust Latam conference, Montevideo Uruguay, March 2019]
Acorn - A small, fast, JavaScript-based JavaScript parser
watt - Runtime for executing procedural macros as WebAssembly
proposal-type-annotations - ECMAScript proposal for type syntax that is erased - Stage 1
prae - prae is a crate that aims to provide a better way to define types that require validation.