R. Kent Dybvig

There is not presently a relocation table at the end of the code object, but I'm open to adding one, and a 2GB code-object size limit doesn't bother me, as...

Extending the existing `ftype-ref` and `ftype-set!` forms to work for bytevectors would add dispatch overhead to the generated code and increase the code size. A better option might be to...

Supporting R7RS is a fine idea as long as doing so doesn't overly complicate the expander, compiler, or run-time system. We should also keep in mind that R7RS is not...

I wouldn't mind changing this if we introduce it for the non-r6rs version of `syntax-rules`. If you expect to use the r6rs version of `syntax-rules` with that srfi, that won't...

That's correct. The c-coded boot-file loader has no way to talk with the Scheme-coded library manager. One way to fix this would be to switch from the C-coded loader to...

I've found the exceptions raised in such cases useful for debugging, so I prefer not to make this change. The lookup routine can catch the exception, e.g., using `guard`, to...

Adding an optional third argument would be fine and would allow a property value of `#f` to be distinguished from no property value.

That sounds like a useful feature, though I worry about spam postings. Would be reasonable for the list to be produced from a database stored in the repository and have...

It sounds like you're building the boot and header files for 32-bit (arm32le) and the c directory for 64-bit. If you mean to build the 32-bit version, you might need...

It doesn't matter which is used in the C code. time_t_bits is defined (as time-t-bits) in the various s directory machine-type def files, along with int_bits (int-bits), long_bits (long-bits), etc.,...