- User Since
- Aug 11 2018, 4:24 PM (48 w, 5 d)
Apr 10 2019
Sorry for the delay. Just catching up on the code this covers, so apologies if the questions don't make sense.
Feb 21 2019
Sorry for the delay here, but this should be ready to go.
Nov 29 2018
I don't think we need to change the serialization format for this: a serialized path beginning with / is already treated as absolute and any other path is already treated as relative, so we don't need a flag to carry that information.
Oct 7 2018
Oct 5 2018
Sep 24 2018
Dropping the module directory entirely and fully resolving paths on serialization
broke some things during deserialization, specifically when the deserializer wanted
to update paths to use an alternate module directory.
Sep 1 2018
fix umbrella writing
I'm not sure this is the best approach, but I wasn't sure of a better one (to support module files w/o absolute paths). Another approach I tried, was relativizing the other input files (from outside the module directory) using chains of ../ (e.g. ../../../../../other/modules/module.modulemap), but this causes issues when symlinks appear in the module directory path. Another potential option could be to add a bit to the serialized module format for each input, to allow some inputs to mark themselves as relative to the CWD, rather than the module directory.