rainbow-identifiers
sixten
Our great sponsors
rainbow-identifiers | sixten | |
---|---|---|
3 | 5 | |
135 | 748 | |
- | - | |
0.0 | 1.8 | |
over 9 years ago | over 3 years ago | |
Emacs Lisp | Haskell | |
- | BSD 3-clause "New" or "Revised" License |
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.
rainbow-identifiers
-
Tree Sitter and the Complications of Parsing Languages
> Giving the same hue to names that look like each other.
Emacs' 'Rainbow Identifiers' does that. I like it.
https://github.com/Fanael/rainbow-identifiers
-
Best syntax highlighting package
I am currently using rainbow identifiers, but I am wondering if there is another package that is better.
-
Practical questions from a lisp beginner
For something fancy, there's also rainbow-blocks and rainbow-identifiers
sixten
-
What do Haskellers think about Rust?
Immutable data structures don't necessarily require more memory: they can avoid deep copies. They are also automatically thread safe without expensive (slow) locking mechanisms. They also don't necessarily reduce cache locality. The reduced cache locality in the case of Haskell (I think) mainly comes from the representation of objects in its implementation (improved STG) which uses extensive boxing and jumps that hinder both spatial and temporal locality (require review/comment from GHC/Computer Architecture experts, take it with a grain of salt). Objects can be much more efficiently represented if not for the need to implement lazy (call-by-need) semantics. See sixten and futhark for examples.
-
Not well known programming languages with interesting features?
[Sixten](https://github.com/ollef/sixten): functional programming with unboxed data by default.
-
Tree Sitter and the Complications of Parsing Languages
I can't answer this well and don't know of any resources, but I have seen it before in the parser for sixten:
https://github.com/ollef/sixten/blob/60d46eee20abd62599badea85774a9365c81af45/src/Frontend/Parse.hs#L458
-
What languages have bit struct / field constructs?
Sixten is a language that allows precise control over memory layout of algebraic data types.
-
Designing a language where all types are memcpy/blittable.
For something more peripherally related, check out Sixten. Its focus is on using unboxed value representations, which is in spirit close to what you are proposing, and some of its ideas might be good inspiration.
What are some alternatives?
rainbow-delimiters - Emacs rainbow delimiters mode
atom-focus-mode - Atom editor extension - fades editor content and highlights only the lines you are working on
tree-hugger - A light-weight, extendable, high level, universal code parser built on top of tree-sitter
aggressive-indent-mode - Emacs minor mode that keeps your code always indented. More reliable than electric-indent-mode.
pony-tutorial - :horse: Tutorial for the Pony programming language
paren-face - A face dedicated to lisp parentheses
felix - The Felix Programming Language
rainbow-blocks - block syntax highlighting in emacs
vscode-theme-alabaster-dark - Dark version of alabaster ported from https://github.com/tonsky/sublime-scheme-alabaster
rust-analyzer - A Rust compiler front-end for IDEs
ante - A safe, easy systems language