soc

One of the issues that would need to be addressed in a better way is `PathBuf.join`. A method that both concatenates a path or completely replaces the existing one based...

@Screwtapello > I'd expect that to be the majority use-case for dealing with user-specified paths. I think it's highly dangerous that ``` path.join("foo/").join("bar") path.join("foo").join("/bar") ``` do completely different things. I...

The full glory of handling Windows paths: https://googleprojectzero.blogspot.de/2016/02/the-definitive-guide-on-win32-to-nt.html TL;DR: Depending on how low-level you want the API to be, you have to handle 7 different path types.

I think if one makes some simplifying assumptions, like - restricting the valid characters to a common subset - not leaking the actual representation of the paths from the `AbsolutePath`/`RelativePath`...

"Use a supported name or go back to `std::Path`". The point is that the use case is largely around files and paths whose name and placement is within control of...

Hi @ieugen, it only means it builds on WASM, but no directories are provided. I'd expect that WASI already offers an API comparable to dirs, would be crazy if they...

@xerial @gotson would a PR that added general support for setting pragmas with properties be accepted?

I'd suggest starting without `scalaVersion`, but not providing Scala libraries by default. (Basically the opposite of `autoScalaLibrary := false`). It would be a lot more consistent with other possible library...

Do we have no bigger ambitions than being a "Scala" build tool? As an example, Gradle has been very successful not being a "Groovy" build tool. I think some outside...

> It's definitely used mostly for Scala projects over any other language, so defaulting to true makes sense. Isn't that confusing cause and effect?