diff options
author | Martin Odersky <odersky@gmail.com> | 2014-04-03 18:12:53 +0200 |
---|---|---|
committer | Dmitry Petrashko <dmitry.petrashko@gmail.com> | 2014-04-08 17:02:29 +0200 |
commit | c6af272d6d68c708cb87b12f25e61dd0a9717f09 (patch) | |
tree | 872d76c6f0c2c63365d8f40e2dc6ad8429524c01 /.gitignore | |
parent | d079c0291289ad9f6517b0b929c4f03ef6b9f082 (diff) | |
download | dotty-c6af272d6d68c708cb87b12f25e61dd0a9717f09.tar.gz dotty-c6af272d6d68c708cb87b12f25e61dd0a9717f09.tar.bz2 dotty-c6af272d6d68c708cb87b12f25e61dd0a9717f09.zip |
Option for testing for double bindings
A double binding is if a named type gets assigned two denotations in the same period. This is
a side-effect and also a race condition, so it's very bad. I am trying to eliminate all causes of this. But one cause which will likely remain are double defitions in a prgram, if a user writes
class C {
val x: Int
val x: Int
}
Then it's really hard to avoid setting two meanings of C.this.x! That's why the testing
against double bindings is enabled by a -YnoDoubleBindings option. The understanding is that
-YnoDoubleBindings should be set only if there are no double def errors anticipated. Otherwise
the program might fail with an assertion error before the double def error is reported.
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions