getPath, getPath2, and getPath3, are all deprecated with no reasoning in favor of getPath4. Why is this? I only use getPath4 or getPath2 - I either need the LazyPath as a string relative to root_dir (in which case I, regrettably, use getPath2), or as a Path (try getPath4). I understand backwards-compatibility, but this seems a little insane and very unintuitive. We should probably figure out what kinds of getPath functions we want before we end up at getPath65535().
Attempt to be backwards compatible, idk why, I’m guessing they didn’t want to update every step that used it.
Either way, it existed for steps to use internally when being executed; since master (0.17) has separated the creation and execution of the build graph to different processes getPath* has been removed entirely on master (0.17).
3 Likes
oh! swag
i should get into 0.17 but I’m not sure what to start with
I’ll share what Andrew shared with me in another thread - std.Build.Graph.path will give you a LazyPath in 0.17, which sounds like what you need.