Conversation
|
Hi @smarter, Thank you for your contribution! We really value the time you've taken to put this together. Before we proceed with reviewing this pull request, please sign the Typesafe Contributors License Agreement: |
|
Can one of the admins verify this patch? |
There was a problem hiding this comment.
This is a breaking (bincompat) change.
There was a problem hiding this comment.
OK, will fix, I have no idea what is and isn't public API :). Is it okay if I push-force my branch or do you prefer code reviews to be addressed in separate commits?
There was a problem hiding this comment.
Part of 1.0 is making that decision and enforcing it. In these 0.13 days, anything that can be accessed, is public :-/
It's not really been decided, but I'm personally happy with history-rewrites and force pushes.
|
This is kind of exciting. I'm surprised it's such a small change. |
|
perhaps instead of the |
|
A setting would be slightly annoying if you want your sbt build to support both Scala and Dotty, you'd have to do |
|
...Unless the setting default value is |
|
Settings generally go into |
This small set of changes, together with the compiler-bridge I wrote (https://github.com/smarter/dotty-bridge) enables us to compile code using Dotty in sbt, see https://github.com/smarter/dotty-example-project for an example.
|
If I make |
That is a very good point.
I think we're good here. |
This small set of changes, together with the compiler-bridge I wrote (https://github.com/smarter/dotty-bridge) enables us to compile code using Dotty in sbt, see https://github.com/smarter/dotty-example-project for an example. Partial forward port of sbt#2344.
This small set of changes, together with the compiler-bridge I wrote
(https://github.com/smarter/dotty-bridge) enables us to compile code
using Dotty in sbt, see https://github.com/smarter/dotty-example-project
for an example.
It'd be great if this could go in 0.13.10 as using a custom sbt is very cumbersome, let me know if there's anything I can do to help with that!