Paulo Matos and I have recently started porting Chez Scheme
to the ARM and RISC-V ISAs. We'll be focusing on the 64-bit
versions. The goal is to get Racket CS to run on those
architectures.
Motivation: ARM has rapidly grown over the years, and there
is speculation that Apple may soon adopt ARM in
On Friday, May 1, 2020 at 1:02:04 PM UTC+8, Sage Gerard wrote:
>
> > The "project" would be the toplevel folder where the source files for a
> Racket application (not a package)
>
> Why can it not be a package? I would be very, very interested in finding a
> way to make this work for
I know this touches on a reason why PLaneT had issues, but I don't understand
how this is a problem. If two versions of the same package are in different
locations on a filesystem and the module resolver can somehow distinguish the
two using collection paths, then how else do they collide?
On 1/5/20 11:18, Jesse Alama wrote:
Paulo Matos and I have recently started porting Chez Scheme
to the ARM and RISC-V ISAs. We'll be focusing on the 64-bit
versions. The goal is to get Racket CS to run on those
architectures.
Motivation: ARM has rapidly grown over the years, and there
is
Thanks! Although I cannot really see the full implications, the basic idea
sounds really great.
DrRacket does share some things, but tries to minimize the sharing; if it
were possible to share less, that'd be great, but maybe that'll end up
falling under the same category as reasons you'd install
I'll try to write out in more detail what the kinds of package
managers Sage is referring to do, to make this clearer for everyone.
The high-level idea is that you have a bunch of directories on your
system(Alex's analogy to git is a good one), and in each of them, your
run appropriate commands
