Programming Languages

1440 readers

5 users here now

Hello!

This is the current Lemmy equivalent of https://www.reddit.com/r/ProgrammingLanguages/.

The content and rules are the same here as they are over there. Taken directly from the /r/ProgrammingLanguages overview:

This community is dedicated to the theory, design and implementation of programming languages.

Be nice to each other. Flame wars and rants are not welcomed. Please also put some effort into your post.

This isn't the right place to ask questions such as "What language should I use for X", "what language should I learn", and "what's your favorite language". Such questions should be posted in /c/learn_programming or /c/programming.

This is the right place for posts like the following:

"Check out this new language I've been working on!"
"Here's a blog post on how I implemented static type checking into this compiler"
"I want to write a compiler, where do I start?"
"How does the Java compiler work? How does it handle forward declarations/imports/targeting multiple platforms/?"
"How should I test my compiler? How are other compilers and interpreters like gcc, Java, and python tested?"
"What are the pros/cons of ?"
"Compare and contrast vs. "
"Confused about the semantics of this language"
"Proceedings from PLDI / OOPSLA / ICFP / "

See /r/ProgrammingLanguages for specific examples

Related online communities

founded 2 years ago

MODERATORS

armchair_progamer@programming.dev

The "Impossible" Optimization (Mojo compile time magic) (verdagon.dev)

submitted 1 week ago by jeff_hykin@lemmy.world to c/programming_languages@programming.dev

2 comments fedilink hide all child comments

I hope more languages get these features

top 2 comments

sorted by: hot top controversial new old

[–] xxce2AAb@feddit.dk 2 points 1 week ago

It's an interesting write up. Unfortunately, many of the execution contexts that'd really benefit from the bespoke per-regex code probably wouldn't appreciate the additional executable size, e.g. embedded applications.

But it certainly has its place elsewhere.

[–] mcmodknower@programming.dev 2 points 1 week ago

"Wait Evan, did you say heap allocation? Isn't heap allocation at compile-time impossible?" ... Though, I'd bet that some Lisps were doing all this back in the 60s and 70s too, as is usually the case!

Yes, macros in lisp are just normal functions running at compile time, taking in the compile time arguments and outputting code.