The case, and a proposal, for elegant syntax in #lang racket2 https://groups.google.com/forum/#!topic/racket-users/ewWuCvbe93k
Notices tagged with lang
-
Christine Lemmer-Webber (cwebber@octodon.social)'s status on Sunday, 14-Jul-2019 17:47:15 UTC Christine Lemmer-Webber -
Christine Lemmer-Webber (cwebber@octodon.social)'s status on Sunday, 14-Jul-2019 16:42:04 UTC Christine Lemmer-Webber Matthew Flatt's keynote at RacketCon ended in a pretty, well... I guess troubling way to me. (Though, I knew it was coming because we discussed it last night.) There's discussion of the underlying main language moving to a non-lispy syntax. One that still supports macros and etc etc, but there's a fear that parentheses aren't as popular so we should shift (#lang racket will remain available, though).
I fear it's a big pivot, and might lose a lot. I've seen such pivots go badly before.
-
Christine Lemmer-Webber (cwebber@octodon.social)'s status on Wednesday, 10-Jul-2019 01:39:07 UTC Christine Lemmer-Webber #lang dungeon is my vague plan for an ocap-safe module layer for Racket
-
Christine Lemmer-Webber (cwebber@octodon.social)'s status on Wednesday, 10-Jul-2019 01:38:45 UTC Christine Lemmer-Webber The thing that's semi-evil is it doesn't *look* like maybe-evil-macro is likely to inject bindings into your current scope. Admittedly this isn't much of a concern in present Racket programs, but could more seriously break security considerations in something like #lang dungeon
-
Christine Lemmer-Webber (cwebber@octodon.social)'s status on Tuesday, 09-Jul-2019 20:07:48 UTC Christine Lemmer-Webber Good news that Matthew Flatt told me they planned for this, and it should be possible for me to make a safe racket #lang
-
Christine Lemmer-Webber (cwebber@octodon.social)'s status on Monday, 08-Jul-2019 17:05:14 UTC Christine Lemmer-Webber Racket is a channel of communication between different language extensions
- You can add layers on layers and before you know it have huge piles
of stuff. And huge piles of stuff with no protections against each
other, things can/will go wrong. (define-syntax)
- Restricitons / constraints on languages sometimes just as important
(#lang + syntax-parse)
- fine-grained embeddings -
Christine Lemmer-Webber (cwebber@octodon.social)'s status on Friday, 12-Apr-2019 13:57:03 UTC Christine Lemmer-Webber -
Hallå Kitteh (clacke@social.heldscal.la)'s status on Friday, 09-Mar-2018 01:51:33 UTC Hallå Kitteh @kensanata Rust is struggling with this. They build the latest Rust using the previous-latest Rust. A podcast I listen to has one guy working at SuSE, and they like many others want to build everything from source. Basically that turned into (a year ago) building 0.1 from OCaml, building 0.2 from 0.1 etc all the way up to wherever they are now.
(I don't know how Rust is versioned, version numbers for illustrative purposes only)
I think people are working on ways to short-circuit some of the version jumps on Rust, like making a C-built Rust-0.x-equivalent.
People on racket-users are discussing making a #lang rust for Racket, but that would be waay off in the future. And the question is always which Rust to target, as it's moving very quickly. -
h@social.coop's status on Monday, 13-Nov-2017 02:35:05 UTC h Anyone dabbling in #Forth here?