home.social

#prescheme — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #prescheme, aggregated by home.social.

  1. PreScheme arena allocator, the funny part is i can just define external C text like in address->color and color-size LOL

    #scheme #prescheme #lisp

  2. PreScheme arena allocator, the funny part is i can just define external C text like in address->color and color-size LOL

    #scheme #prescheme #lisp

  3. PreScheme arena allocator, the funny part is i can just define external C text like in address->color and color-size LOL

    #scheme #prescheme #lisp

  4. dynamic array in PreScheme

    prescheme from scheme48 source in ps-compiler directory, not from restoration prescheme

    #lisp #scheme #prescheme

  5. dynamic array in PreScheme

    prescheme from scheme48 source in ps-compiler directory, not from restoration prescheme

    #lisp #scheme #prescheme

  6. dynamic array in PreScheme

    prescheme from scheme48 source in ps-compiler directory, not from restoration prescheme

    #lisp #scheme #prescheme

  7. @daviwil #systemcrafters #sigil I’m really excited to see what sigil could actually be. I really envision a flutter like UI kit using #scheme and able to compile to wasm. Is there any interest with #prescheme , possibly have sigil compile down to C?

  8. @daviwil #systemcrafters #sigil I’m really excited to see what sigil could actually be. I really envision a flutter like UI kit using #scheme and able to compile to wasm. Is there any interest with #prescheme , possibly have sigil compile down to C?

  9. @daviwil #systemcrafters #sigil I’m really excited to see what sigil could actually be. I really envision a flutter like UI kit using #scheme and able to compile to wasm. Is there any interest with #prescheme , possibly have sigil compile down to C?

  10. @daviwil #systemcrafters #sigil I’m really excited to see what sigil could actually be. I really envision a flutter like UI kit using #scheme and able to compile to wasm. Is there any interest with #prescheme , possibly have sigil compile down to C?

  11. Whatever happened to the restoration project? Was it abandoned?

    prescheme.org/

    codeberg.org/prescheme/presche

  12. So I guess it makes more sense to create wrappers from rust to C then create #guile bindings from the C code. #niri #guile #scheme, maybe is a great time to learn #prescheme ?

  13. So I guess it makes more sense to create wrappers from rust to C then create #guile bindings from the C code. #niri #guile #scheme, maybe is a great time to learn #prescheme ?

  14. So I guess it makes more sense to create wrappers from rust to C then create #guile bindings from the C code. #niri #guile #scheme, maybe is a great time to learn #prescheme ?

  15. So I guess it makes more sense to create wrappers from rust to C then create #guile bindings from the C code. #niri #guile #scheme, maybe is a great time to learn #prescheme ?

  16. Is #prescheme still being worked on? Is #gerbil worth it? What other #lisp #scheme dialects would be great for systems programming?

  17. Is #prescheme still being worked on? Is #gerbil worth it? What other #lisp #scheme dialects would be great for systems programming?

  18. Is #prescheme still being worked on? Is #gerbil worth it? What other #lisp #scheme dialects would be great for systems programming?

  19. Is #prescheme still being worked on? Is #gerbil worth it? What other #lisp #scheme dialects would be great for systems programming?

  20. I'd love to get an update on what's going on with #PreScheme, but alas:

    - There's only been a single progress report posted on prescheme.org, over a year ago
    - @flatwhatson hasn't posted on Mastodon in many months

    I worry that the Pre-Scheme project might have died a quiet death.

  21. I'd love to get an update on what's going on with #PreScheme, but alas:

    - There's only been a single progress report posted on prescheme.org, over a year ago
    - @flatwhatson hasn't posted on Mastodon in many months

    I worry that the Pre-Scheme project might have died a quiet death.

  22. I'd love to get an update on what's going on with #PreScheme, but alas:

    - There's only been a single progress report posted on prescheme.org, over a year ago
    - @flatwhatson hasn't posted on Mastodon in many months

    I worry that the Pre-Scheme project might have died a quiet death.

  23. I'd love to get an update on what's going on with #PreScheme, but alas:

    - There's only been a single progress report posted on prescheme.org, over a year ago
    - @flatwhatson hasn't posted on Mastodon in many months

    I worry that the Pre-Scheme project might have died a quiet death.

  24. I'd love to get an update on what's going on with #PreScheme, but alas:

    - There's only been a single progress report posted on prescheme.org, over a year ago
    - @flatwhatson hasn't posted on Mastodon in many months

    I worry that the Pre-Scheme project might have died a quiet death.

  25. Small Headed Programming by Pjotr Prins

    looks really nice (for Pythonistas think Cython but this transpiles to proper C, just like transpiles a C# like language to C)

    Readable Lisp, readable C

    fosdem.org/2025/schedule/event


  26. @kaveman @lisp_discussions CRUNCH looks excellent! I'm very glad that the work on #prescheme has encouraged others to experiment with the combination of static typing, minimal runtime, and Scheme metaprogramming. Felix has covered a lot of ground on the language design & tooling, I'll definitely be keeping CRUNCH compatibility in mind as the Pre-Scheme restoration progresses.

  27. @kaveman @lisp_discussions CRUNCH looks excellent! I'm very glad that the work on #prescheme has encouraged others to experiment with the combination of static typing, minimal runtime, and Scheme metaprogramming. Felix has covered a lot of ground on the language design & tooling, I'll definitely be keeping CRUNCH compatibility in mind as the Pre-Scheme restoration progresses.

  28. @kaveman @lisp_discussions CRUNCH looks excellent! I'm very glad that the work on #prescheme has encouraged others to experiment with the combination of static typing, minimal runtime, and Scheme metaprogramming. Felix has covered a lot of ground on the language design & tooling, I'll definitely be keeping CRUNCH compatibility in mind as the Pre-Scheme restoration progresses.

  29. Thanks @pjotrprins, #prescheme is definitely lacking in documentation and examples right now, and I know that people are eager to dive in. Unfortunately it's not very user-friendly in its current state; the language didn't see much use outside of its initial use-case, and it shows!

    After the port is complete, I'll be making a number of language and tooling changes to improve this situation. Once those are settled, I'll move on to documentation and guides to make the language accessible to a wider audience.

    An outline of the planned changes can be found here: prescheme.org/roadmap.html

    @nlnet

  30. Thanks @pjotrprins, #prescheme is definitely lacking in documentation and examples right now, and I know that people are eager to dive in. Unfortunately it's not very user-friendly in its current state; the language didn't see much use outside of its initial use-case, and it shows!

    After the port is complete, I'll be making a number of language and tooling changes to improve this situation. Once those are settled, I'll move on to documentation and guides to make the language accessible to a wider audience.

    An outline of the planned changes can be found here: prescheme.org/roadmap.html

    @nlnet

  31. Thanks @pjotrprins, #prescheme is definitely lacking in documentation and examples right now, and I know that people are eager to dive in. Unfortunately it's not very user-friendly in its current state; the language didn't see much use outside of its initial use-case, and it shows!

    After the port is complete, I'll be making a number of language and tooling changes to improve this situation. Once those are settled, I'll move on to documentation and guides to make the language accessible to a wider audience.

    An outline of the planned changes can be found here: prescheme.org/roadmap.html

    @nlnet

  32. It's time for an update on the Pre-Scheme Restoration project!

    TL;DR: The compiler is approximately 75% ported to Chibi, Sagittarius and Guile, with Unsyntax expander integration underway. We've also got a new R7RS compatibility layer for Scheme 48, and a bunch of tooling written with Scsh.

    Thanks to @nlnet for supporting this project under the NGI Zero Core program.

    See my update post for more details: prescheme.org/posts/first-repo

    #scheme #prescheme

  33. It's time for an update on the Pre-Scheme Restoration project!

    TL;DR: The compiler is approximately 75% ported to Chibi, Sagittarius and Guile, with Unsyntax expander integration underway. We've also got a new R7RS compatibility layer for Scheme 48, and a bunch of tooling written with Scsh.

    Thanks to @nlnet for supporting this project under the NGI Zero Core program.

    See my update post for more details: prescheme.org/posts/first-repo

    #scheme #prescheme

  34. It's time for an update on the Pre-Scheme Restoration project!

    TL;DR: The compiler is approximately 75% ported to Chibi, Sagittarius and Guile, with Unsyntax expander integration underway. We've also got a new R7RS compatibility layer for Scheme 48, and a bunch of tooling written with Scsh.

    Thanks to @nlnet for supporting this project under the NGI Zero Core program.

    See my update post for more details: prescheme.org/posts/first-repo

    #scheme #prescheme

  35. It's time for an update on the Pre-Scheme Restoration project!

    TL;DR: The compiler is approximately 75% ported to Chibi, Sagittarius and Guile, with Unsyntax expander integration underway. We've also got a new R7RS compatibility layer for Scheme 48, and a bunch of tooling written with Scsh.

    Thanks to @nlnet for supporting this project under the NGI Zero Core program.

    See my update post for more details: prescheme.org/posts/first-repo

    #scheme #prescheme

  36. It's time for an update on the Pre-Scheme Restoration project!

    TL;DR: The compiler is approximately 75% ported to Chibi, Sagittarius and Guile, with Unsyntax expander integration underway. We've also got a new R7RS compatibility layer for Scheme 48, and a bunch of tooling written with Scsh.

    Thanks to @nlnet for supporting this project under the NGI Zero Core program.

    See my update post for more details: prescheme.org/posts/first-repo

    #scheme #prescheme

  37. Wow @aartaka, this is excellent, thanks!

    This beautifully demonstrates a number of nice things about #prescheme:

    - The power of using #scheme macros to define language constructs.
    - The flexibility of full type inference as the base model for static typing.
    - The efficiency of having a proper optimizing compiler (in this case, dead code elimination).

    Very cool!

  38. Wow @aartaka, this is excellent, thanks!

    This beautifully demonstrates a number of nice things about #prescheme:

    - The power of using #scheme macros to define language constructs.
    - The flexibility of full type inference as the base model for static typing.
    - The efficiency of having a proper optimizing compiler (in this case, dead code elimination).

    Very cool!

  39. Wow @aartaka, this is excellent, thanks!

    This beautifully demonstrates a number of nice things about #prescheme:

    - The power of using #scheme macros to define language constructs.
    - The flexibility of full type inference as the base model for static typing.
    - The efficiency of having a proper optimizing compiler (in this case, dead code elimination).

    Very cool!

  40. Wow @aartaka, this is excellent, thanks!

    This beautifully demonstrates a number of nice things about #prescheme:

    - The power of using #scheme macros to define language constructs.
    - The flexibility of full type inference as the base model for static typing.
    - The efficiency of having a proper optimizing compiler (in this case, dead code elimination).

    Very cool!

  41. @aartaka I was curious how SRFI 253 could be supported without predicates, but I see the implementation-specific macros treat the predicates as identifier literals and translate them into the equivalent type names. That approach could definitely be made to work for #prescheme, nice!

    I think the situation with support for explicit types in Scheme can be explained by survivorship bias. Programmers who strongly prefer type declarations are better served by other languages, so we're left with a community that are generally happy to omit them. FFI's are just one place where they're really not optional.

    Cheers!

    @daviwil

  42. @aartaka I was curious how SRFI 253 could be supported without predicates, but I see the implementation-specific macros treat the predicates as identifier literals and translate them into the equivalent type names. That approach could definitely be made to work for #prescheme, nice!

    I think the situation with support for explicit types in Scheme can be explained by survivorship bias. Programmers who strongly prefer type declarations are better served by other languages, so we're left with a community that are generally happy to omit them. FFI's are just one place where they're really not optional.

    Cheers!

    @daviwil