Karoy Lorentey
Karoy Lorentey
> On 2016-11-09, at 00:30, Tim Vermeulen [email protected] wrote: > I did a bunch of tests, and found something really interesting. If I copy the entire library to my project...
The technical limitation was resolved by the introduction of `@inlinable`, but this package has not adopted it. We're working on a new "official" implementation in https://github.com/apple/swift-collections/issues/1 -- I expect that...
👍 Anything works! ☺️
@benoit-pereira-da-silva Thank you! Could you please remove the extra commits? Codable support should go in a separate PR.
Hi @seivan; I sent an invite with commit access. Thank you for volunteering to do this!
> Personally, I think the concept of a process-wide, mutable "current working directory" is a serious mistake; a dinosaur we should allow to go extinct. Swift System's job is to...
> I think it makes sense to also land changeWorkingDirectory in the same release as this, but where would it live? (This doesn't have to block this PR, of course)....
I agree with pretty much every word, but I don't think it would be practical for System not to expose `getcwd` -- the thing is, the concept of a current...
> System already exposes it through the behavior of `open` when given a relative file path. We definitely need a wrapper for `openat`, btw! It's sort of shameful we didn't...
Yep, sadly we cannot remove the existing, throwing entry point. We could introduce a new non-throwing one while keeping the original around, but unfortunately it would need to have a...