5 ms·

> "cool, a way to get the binaries small enough for embedded" lol, I didn't even realize the wrong associations I would create here. Glad you liked it anyway.

by ralfj 4y ago

> "cool, a way to get the binaries small enough for embedded" lol, I didn't even realize the wrong associations I would create here. Glad you liked it anyway. :) I guess my choice of name was not great. I also considered pseudo-MIR but that didn't really capture it, either. And "formally specified fragment of Rust" isn't very catchy.^^ "CoreRust", maybe it should have been "CoreRust"...

cestith 4y ago
Using "mini" to mean a subset of the language rather than a version for small systems has precedent. For example in the Perl community, miniperl is a subset of Perl. It's mostly used to bootstrap builds of the full language, but in theory can be used separately as a restricted programming language. It's also the name of a module, ExtUtils::Miniperl, for Perl (https://metacpan.org/pod/ExtUtils::Miniperl https://metacpan.org/pod/ExtUtils::Miniperl) that builds miniperlmain.c and perlmain.c files to bootstrap the compilation of the language system. This is not to be confused with the Raku project on Github called "miniPerl" (https://github.com/grondilu/miniPerl https://github.com/grondilu/miniPerl) which compiles subsets of Perl via the Lambda calculus to JavaScript output. I'd personally pretty much always expect "mini" or "r" (as in "rperl", a restricted subset of Perl with C++ connections) versions of a language to be restricted subsets for some purpose (rperl's is to give away flexibility for performance while maintaining a good portion of the original language). I've seen an "e" or "emb" prefix or a "small", "tiny", "micro" or "µ" (or "u") prefix to mean a small toolchain version several places, like SmallC or uclibc or Mikroe's mikroC (https://www.mikroe.com/mikroc https://www.mikroe.com/mikroc). It wouldn't surprise me to see a "nano" version of a language tool either. Sometimes these are subsets as well, but to fit the size constraints of the target rather than for constraining the input for its own sake.
- lizmat 4y ago
  I guess you could argue that the Raku Programming Language also has its "mini" version, to build the actual language on. In Raku's case, it's called NQP (which used to stand for "Not Quite Perl", but now is just considered to be "NQP"). Programming in NQP is troublesome, but it is fast and it is self-hosting.

by ralfj 4y ago

cestith 4y ago

Using "mini" to mean a subset of the language rather than a version for small systems has precedent. For example in the Perl community, miniperl is a subset of Perl. It's mostly used to bootstrap builds of the full language, but in theory can be used separately as a restricted programming language. It's also the name of a module, ExtUtils::Miniperl, for Perl (https://metacpan.org/pod/ExtUtils::Miniperl https://metacpan.org/pod/ExtUtils::Miniperl) that builds miniperlmain.c and perlmain.c files to bootstrap the compilation of the language system. This is not to be confused with the Raku project on Github called "miniPerl" (https://github.com/grondilu/miniPerl https://github.com/grondilu/miniPerl) which compiles subsets of Perl via the Lambda calculus to JavaScript output. I'd personally pretty much always expect "mini" or "r" (as in "rperl", a restricted subset of Perl with C++ connections) versions of a language to be restricted subsets for some purpose (rperl's is to give away flexibility for performance while maintaining a good portion of the original language). I've seen an "e" or "emb" prefix or a "small", "tiny", "micro" or "µ" (or "u") prefix to mean a small toolchain version several places, like SmallC or uclibc or Mikroe's mikroC (https://www.mikroe.com/mikroc https://www.mikroe.com/mikroc). It wouldn't surprise me to see a "nano" version of a language tool either. Sometimes these are subsets as well, but to fit the size constraints of the target rather than for constraining the input for its own sake.

lizmat 4y ago
I guess you could argue that the Raku Programming Language also has its "mini" version, to build the actual language on. In Raku's case, it's called NQP (which used to stand for "Not Quite Perl", but now is just considered to be "NQP"). Programming in NQP is troublesome, but it is fast and it is self-hosting.