mirror of
https://github.com/sbt/sbt.git
synced 2026-09-04 00:41:32 +02:00
Antonio Cunei
9aa0985f4b
The implementation of Relation should in theory make no difference whether an element is unmapped, or whether it is mapped to an empty set. One of the changes in322f6de655introduced an optimization to the '+' operation on Relations that, in theory, should have made no difference to the semantic. The result of that optimization is that some mappings of the form "elem -> Set()" are no longer inserted in the forwardMap of the Relation. Unfortunately, the change resulted in the breakage of #1430, causing "set every" to behave incorrectly. There must be, somewhere in the code, a test on the presence of a key rather than an access via <relation>.get(), or some other access that bypasses the supposed semantic equivalence described above. I spent several hours trying to track down exactly the offending test, without success. By undoing the relevant change in322f6de655, "set every" works again. That however offers no guarantee that everything else will keep working correctly; the underlying quirk in the code that depends on this supposedly inessential detail is also still lurking in the code, which is less than ideal.
sbt
sbt is a build tool for Scala, Java, and more. For general documentation, see http://www.scala-sbt.org/.
Issues and Pull Requests
Please read CONTRIBUTING carefully before opening a GitHub Issue. The short version: try StackOverflow and sbt-dev. Don't open an Issue.
sbt 0.13
This is the 0.13.x series of sbt.
- Setup: Describes getting started with the latest binary release.
- FAQ: Explains how to get help and more.
- Google Code: hosts sbt 0.7.7 and earlier versions
license
See LICENSE.