3 ms·
I followed some of the discussions of the porting to guile3. I have been amazed at what kind of code guile1.8 allowed, with _no_ separation of macro expansion a
by bjoli 7y ago
I followed some of the discussions of the porting to guile3. I have been amazed at what kind of code guile1.8 allowed, with _no_ separation of macro expansion and runtime.:
(defmacro (foo bar)
(define (baz n) (bar 4 n))
baz)
((foo +) 4)
would work just fine. No separation between runtime and compile time. this hasn't been the case since 2.0, but 1.8 is still used places. Hopefully their port to guile 3 works so that they can reap the benefits of the work out in there over the last 10 years.
- mgubi 7y agoThe port is ready and working. We are waiting the release of TeXmacs 2.1 soon and then we will start working to integrate it to the main branch. TeXmacs will run with Guile 3.0 with the codebase fully compiled. It should improve loading times and some critical operations, but not benchmarks have been done yet.