Sure, I understand that there are a lot of moving parts. Please do keep me posted, I'm looking for opportunities to contribute, as per my skills) On Feb 11, 2017 6:07 PM, "Matthew Flatt" <[email protected]> wrote:
> Hi Abhinav, > > At Sat, 11 Feb 2017 16:32:47 +0530, Abhinav Sharma wrote: > > 1. Is it possible to use any racket lib written in other dialects like > > hackett or rosette in racket - directly or byte-code compiled? > > When you run from source, it is compiled internally to bytecode, so > using the library source or in bytecode form should be the same. > > > > 2. Which files are undergoing a change from *.c to *.rkt extension? Apart > > from the Leif Andersen's repo is there any other resources that'd help me > > understand the proposed changes better? > > See the "linklet" branch of the "mflatt/racket" repo on GitHub: > > https://github.com/mflatt/racket/tree/linklet > > The "pkgs" directory has new subdirectories: > > * "expander" --- an essentially complete rewrite of the macro > expander, module system, and reader > > * "regexp" --- an essentially complete rewrite of the regexp matcher > > * "path" --- a barely started rewrite of path operations > > * "port" --- a barely started rewrite of input and output ports > > Next on my list is the thread and events subsystem, and so on. The goal > is to replace nearly all of the C code with Racket implementations. > > > > 3. What does the team feel about the C-codebase and about plans to > > modernize it - what's the roadmap? > > I hope it's ok if I defer this question for a little while (a couple of > weeks at most), since I should be able to give a better answer soon. > > > Matthew > > -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CAAub%2BCemu6W8iP67-Lptfcx7FBWiYRDp5cY-uu-nn8xkk-UpPQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
