Re: [racket-users] counterintuitive behavior of namespace-require

I see, thanks for the explanation! On Monday, January 6, 2020 at 10:28:21 PM UTC-5, Matthew Flatt wrote: > > The problem is that `namespace-require` has to first resolve the > `racket` module path, and the module name resolver uses the current > namespace as determined by `current-namespace` ---

Re: [racket-users] counterintuitive behavior of namespace-require

The problem is that `namespace-require` has to first resolve the `racket` module path, and the module name resolver uses the current namespace as determined by `current-namespace` --- which means that the resolver loads the `racket` module into the wrong namespace. I doubt that we can change that

[racket-users] counterintuitive behavior of namespace-require

Hi, I have encountered a counterintuitive behavior of namespace-require and wonder if it is a bug. Basically, namespace-require behaves differently when the target namespace is passed by parameterizing current-namespace, compared to when the optional namespace parameter is used. For example, th

Re: [racket-users] Re: macOS 10.10 Yosemite?

On Jan 4, 2020, at 4:04 PM, Robby Findler wrote: > No Yosemite users to be found? At some point, I should build a Yosemite VM in VMWare for testing purposes but it isn't a priority at the moment. The thing is that Yosemite is one of those versions of macOS where the use cases to stick with it