Viewing profile — stchang

Correct. More specifically, type checking is performed as part of macro expansion, which happens at compile-time.

Thanks for the comment!

The submitted link might be an older preprint. Here is the official acm link to the paper: https://dl.acm.org/doi/10.1145/3371071

Awesome! Would love to check it out once you have a prototype.

It could, though it's not clear whether it would be an improvement. Typed Racket uses macro expansion to translate its typed surface language into a typed core language, and then t…

Typed Racket uses macro expansion to translate its typed surface language into a typed core language, and then typechecks the core language. Our approach uses macro expansion to ty…

> Can you do dependent types? Yes. For example, see https://github.com/wilbowma/cur

Minor correction, Matthias created Racket.

It's a misunderstanding that has unfortunately caught on among many Haskell programmers. People who say "macros are only useful in strict languages" mistakenly think that macros ca…

FWIW, the phase system that is the main topic of the article was created for Racket [1], though some Scheme macro systems have since adopted this Racket innovation. [1]: https://ww…

Here's some more context info for the paper: http://2015.ecoop.org/event/research-track-towards-practical...

Yup! I meant that they switched from GOAL to Racket for the PS3. Here's a summary from a presentation at the CUFP workshop (likely a shorter version of the slides above): Dan Liebg…

They switched to Racket when moving to the PS3. Here's a talk discussing the use of Racket in developing The Last of Us: https://www.youtube.com/watch?v=oSmqbnhHp1c

When moving to PS3, they used Racket instead. https://www.youtube.com/watch?v=oSmqbnhHp1c

> (presumably because you have lives) Why does it matter what people do for leisure?

All of Racket's `#lang` family of languages are implemented with macros on top of core Racket. For example, Scribble, mentioned in another comment, is the documentation language us…

> Haskell, by its lazy evaluation, is basically a macro-only language This is not correct. To understand why, please see Ryan Culpepper's answer to this SO question: http://stackov…