Re: [racket-users] how to convert encoded path to something build-path can use?

Thanks! We were previously manually processing the files from current-library-collection-links, but using `links` saves ~100 lines of code. On Fri, May 21, 2021 at 11:50 AM Matthew Flatt wrote: > > Yes, the format changed in that commit. > > The `decode-link-path` function is not meant to be

Re: [racket-users] how to convert encoded path to something build-path can use?

Yes, the format changed in that commit. The `decode-link-path` function is not meant to be public, although it could be exposed. But for an approach that works now and with older versions, the API you want is `links` from `setup/link`, possibly like this: (links #:file (find-links-file)

[racket-users] how to convert encoded path to something build-path can use?

Hi, It seems that, since 8.1, the format of paths in links.rktd has changed? Are there new API fns that deal with this new kind of encoded path? Or what is the recommended way to process them? Something like this? (Is this `decode-link-path` public? I couldnt find it)