Racket definition messages vague compared to other implementations
It seems like the Racket function definitions that geiser is providing are pretty vague.
I installed guile just to get a comparison:
I'd be interested in looking into this issue actually, do you have any pointers as to where to start? Maybe this is just a limitation of how Racket exports symbols?
Looks like it's down to
locations.rkt/symbol-location. The module name for a lot of core functionality in racket is resolving to
%runtime and the like, instead of actual files for geiser to go and parse. I updated
symbol-location* to resolve to an actual file path with:
(resolved-module-path-name (module-path-index-resolve (third binding))))
but that just resolves to
...racket/collects/racket/main.rkt, which is just where the majority of racket's base symbols are required and then provided from.
It looks like the vague function definitions for most of the core library is because, since no source file is found, it just ends up calling
More to come, if/when I get back to this.