clojure-style-guide
Crafting Interpreters
Our great sponsors
clojure-style-guide | Crafting Interpreters | |
---|---|---|
15 | 45 | |
3,976 | 7,995 | |
- | - | |
2.9 | 0.0 | |
23 days ago | 6 days ago | |
HTML | ||
- | GNU General Public License v3.0 or later |
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.
clojure-style-guide
-
XML is better than YAML
Fixed link to that style guide entry: https://guide.clojure.style/#opt-commas-in-map-literals
Per that style guide, the above map would be formatted like this (on HN, just indent by two spaces):
{:a 1
-
What makes Clojure better than X for you?
Basically, you learn the expected places to put whitespace, make sure to edit your code accordingly and all of the parens will be automatically closed and adjusted. Using parinfer—which you can also combine with the more traditional paredit—makes writing Clojure code a lot like writing Python.
-
Poignant perspective I found about Clojure's community in r/ExperiencedDevs
Also, there are guidelines, the styleguide, clj-kondo, kibit etc. And if you don't review your interns/juniors code to teach them good practices - you're doing it wrong (well, this one is true for any practical PL out there).
-
How to learn Clojure idioms?
Another good resource is https://guide.clojure.style/ -- the (unofficial) community style guide for Clojure.
-
4-space indents?
It's not an answer to your question but i can refer you to https://github.com/bbatsov/clojure-style-guide
-
Wrote one of my first clojure programs (tic-tac-toe). Any constructive criticism would be greatly appreciated.
Formatting is not that great, see https://github.com/bbatsov/clojure-style-guide btw
- Want to get into closure, but struck at practice
- [clojure-noob][code-review]I've written my first piece of code in clojure, can you guys review it ?
-
Free 500+ books and learning resources for every programmer.
The Clojure Style Guide
-
JavaScript Developer Lessons: Code Styling Guide
The Clojure Style Guide - A community coding style guide for the Clojure programming language.
Crafting Interpreters
- Crafting Interpreters
-
The Top 10 GitHub Repositories Making Waves 🌊📊
Build an Interpreter (Chapter 14 on is written in C)
-
Writing a Debugger from Scratch: Breakpoints
I’m guessing you’ll have to work with the scopes in the resolver:
https://github.com/munificent/craftinginterpreters/blob/mast...
I was asking this myself this while reading the book "Crafting Interpreters". I posted a few resources I found on an issue about implementing debuggers [] although honestly I still haven't gotten down to read all of them (or to implement a debugger! :-/).
--
: https://github.com/munificent/craftinginterpreters/issues/92...
-
loxcraft: a compiler, language server, and online playground for the Lox programming language
Better open an issue/request wiki edit at https://github.com/munificent/craftinginterpreters/wiki/Lox-implementations
- Gigachad Ken Thomson.
-
Show HN: Yaksha Programming Language
I'm late to the party, but I want to say thank you for sharing this. It's inspiring to look at how much you've built and (hopefully) enjoyed the process of building! I'm loving everything -- your site, your language design, your docs, your builtin libraries, your dev tools. Beyond impressive. People like you are the ones who make HN one of my best places on the internet.
For context on where I'm coming from, about two weeks ago I picked up Crafting Interpreters [1] for fun. I'm finding your clear-yet-concise Compiler internals [2] to be particularly compelling reading, and jumping back and forth between those "how this all works" docs and the live example of this language you actually built do a WASM-compiled tree-blowing-in-the-wind animation is just... just wow. So freaking cool!
I also enjoyed reading the comment thread that inspired you to start on Yaksha and seeing how this project has a wholesome start as inspiration-by-programming-hero. I hope you recognize that a few years later you've now ascended from inspiree to inspirer. I also hope you're still having tons of fun building out Yaksha!
[1] https://www.craftinginterpreters.com/
[2] https://yakshalang.github.io/documentation.html#compiler-int...
- Keeping track of returned and break-ed values between code blocks
-
How do you start your own programming language?
There are books which will talk you through the process. Crafting Interpreters is highly spoken of; I used Writing an Interpreter in Go, because I like Go. Then there's Compilers: Principles, Techniques, and Tools (the "Dragon Book"). This is considered heavy, but a classic, it's been around since '86.
-
Designing a new language
I cannot recommend Crafting Interpreters by Robert Nystrom enough, it covers a lot of the stuff you need to know, completely for free.
What are some alternatives?
git-internals-pdf - PDF on Git Internals
You-Dont-Know-JS - A book series on JavaScript. @YDKJS on twitter.
prettier - Prettier is an opinionated code formatter.
tinyrenderer - A brief computer graphics / rendering course
paip-lisp - Lisp code for the textbook "Paradigms of Artificial Intelligence Programming"
CppCoreGuidelines - The C++ Core Guidelines are a set of tried-and-true guidelines, rules, and best practices about coding in C++
30-days-of-elixir - A walk through the Elixir language in 30 exercises.
papers-we-love - Papers from the computer science community to read and discuss.
project-based-learning - Curated list of project-based tutorials
web-dev-golang-anti-textbook - Learn how to write webapps without a framework in Go.
pyright-python - Python command line wrapper for pyright, a static type checker