summaryrefslogtreecommitdiff
path: root/bincompat-backward.whitelist.conf
diff options
context:
space:
mode:
authorSom Snytt <som.snytt@gmail.com>2016-10-26 11:45:55 -0700
committerSom Snytt <som.snytt@gmail.com>2016-11-17 07:49:03 -0800
commitfbcfba212fff76272c509c6781ea2a2897d84bff (patch)
tree2ff682f1233400ad9626294c1f6ca6e0d17666fb /bincompat-backward.whitelist.conf
parent51e77408160fcef8b8c0669e1c62ec9a36f3b606 (diff)
downloadscala-fbcfba212fff76272c509c6781ea2a2897d84bff.tar.gz
scala-fbcfba212fff76272c509c6781ea2a2897d84bff.tar.bz2
scala-fbcfba212fff76272c509c6781ea2a2897d84bff.zip
SI-10007 sys.process thread sync
A previous change to replace `SyncVar.set` with `SyncVar.put` breaks things. This commit tweaks the thread synchronizing in `sys.process` to actually use `SyncVar` to sync and pass a var. Joining the thread about to exit is superfluous. A result is put exactly once, and consumers use non-destructive `get`. Note that as usual, avoid kicking off threads in a static context, since class loading cycles are somewhat dicier with 2.12 lambdas. In particular, REPL is a static context by default. SI-10007 Clarify deprecation message The message on `set` was self-fulfilling, as it didn't hint that `put` has different semantics. So explain why `put` helps avoid errors instead of creating them. SI-10007 Always set exit value Always put a value to exit code, defaulting to None. Also clean up around tuple change to unfortunately named Future.apply. Very hard to follow those types. Date command pollutes output, so tweak test.
Diffstat (limited to 'bincompat-backward.whitelist.conf')
0 files changed, 0 insertions, 0 deletions