Hi All,
There have been some fantastic entries! but there are still more stickers
to be had.
https://github.com/standard-fish/summer-competititon-2019
https://github.com/standard-fish/summer-competititon-2019/blob/master/TOOLS.md
I know you are all motivated by the joy learning, but I might
Atlas, I get the impression, from the impassioned discussion thus far,
that a lot of the community really wants an s-expression syntax (and
print form for data) to be not merely backwards-compatibile supported,
*but to remain fully a "first-class citizen"*.
I suspect that the top-level
Matthew posted an (IMO) clear explanation of the state of the thinking here
earlier. tl;dr: sexpressions will never be abandoned and backwards
compatibility with existing languages will be maintained for the
foreseeable future.
... but read his message if you are worried. I believe it is
I just see pretty broad discussion of new non s-expression syntax on GitHub
with lots of code examples and even some draft specification.
Here https://github.com/racket/racket2-rfcs/issues/3
And here https://github.com/racket/racket2-rfcs/pull/88/
And I just cannot understand whats going on.
On Sun, 11 Aug 2019 07:51:53 -0700 (PDT)
Atlas Atlas wrote:
> I don't known how racket is managed. Can someone clarify for me the
> future of Racket.
>
>
> Is abandoning s-expressions is sealed decision?
>
>
> What chances that this will happen? 10% 50% 80% 100%?
>
As far as I understood
I don't known how racket is managed. Can someone clarify for me the future
of Racket.
Is abandoning s-expressions is sealed decision?
What chances that this will happen? 10% 50% 80% 100%?
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
6 matches
Mail list logo
