It’s in the expander
Very nice shout-out to Racket from Chris Kipps’s Scala-oriented <https://www.tooling-talks.com/|Tooling Talks> podcast 2021–10–01 http://twitter.com/share?text=Listening+to+%22Guillaume+Martres%3A+An+Interactive+Compiler%22+at+&url=https%3A%2F%2Fwww.buzzsprout.com%2F1830936%2F9288213-guillaume-martres-an-interactive-compiler at 56:17
Chris Kipp said this link might work better: https://tooling-talks.buzzsprout.com/1830936/9288213?t=3377
There could be a bytes->symbol function to save the copy
is there a library to create a pict out of BNF?
This doesn’t produce a pict, but it’s better than nothing: https://docs.racket-lang.org/scribble/bnf.html
Use redex and render-language?
okay, how do I make the render-language font size larger
er, rather, language->pict, since that’s recommended for slideshow usage
nvm, (parameterize ([default-font-size ...]) ...)
That would be nice.
@samth bytes->symbol would have the same encoding issue, right? i.e. would it need to be something like bytes->symbol/utf-8 ?
Yes, it would
Ok, I’ll look into it.
@samth looking for the source to string->symbol in Emacs gave me: Defined in #%%kernel -- source not available I’m thinking this may be above my current pay grade :(
I’m not even sure when it should be utf–8 vs. just e.g. latin1? I haven’t worked on web stuff super recently. If it’s a POST body from an HTML page you authored with a meta tag saying utf–8, I guess it’s safe to assume utf–8? But if a user is doing some GET with query params, and that ends up in request-bindings/raw, should that be latin1? Not sure.
Anyway it’s talking past the close, but you’d have those same questions using string keys for JSON.
It kind of underlines how converting to symbols is by far the simplest “half” of this, it’s bytes to string that is the usual can of worms. :slightly_smiling_face:
If you’ve successfully/correctly made a string, the step converting to symbol is kind of a no-brainer by comparison.