Skip to content
This repository
Browse code

Unprivatize methods in SyncVar.

These are still used in SBT 0.13.0-M2.

This is a partial revert of ac990c1.
  • Loading branch information...
commit 37707cd8bd20643574d746b294016963a99431d3 1 parent e36bb0b
Jason Zaugg retronym authored

Showing 1 changed file with 4 additions and 2 deletions. Show diff stats Hide diff stats

  1. +4 2 src/library/scala/concurrent/SyncVar.scala
6 src/library/scala/concurrent/SyncVar.scala
@@ -79,7 +79,8 @@ class SyncVar[A] {
79 79 // whether or not the SyncVar is already defined. So, set has been
80 80 // deprecated in order to eventually be able to make "setting" private
81 81 @deprecated("Use `put` instead, as `set` is potentionally error-prone", "2.10.0")
82   - private[scala] def set(x: A): Unit = setVal(x)
  82 + // NOTE: Used by SBT 0.13.0-M2 and below
  83 + def set(x: A): Unit = setVal(x)
83 84
84 85 /** Places a value in the SyncVar. If the SyncVar already has a stored value,
85 86 * it waits until another thread takes it */
@@ -98,7 +99,8 @@ class SyncVar[A] {
98 99 // whether or not the SyncVar is already defined. So, unset has been
99 100 // deprecated in order to eventually be able to make "unsetting" private
100 101 @deprecated("Use `take` instead, as `unset` is potentionally error-prone", "2.10.0")
101   - private[scala] def unset(): Unit = synchronized {
  102 + // NOTE: Used by SBT 0.13.0-M2 and below
  103 + def unset(): Unit = synchronized {
102 104 isDefined = false
103 105 value = None
104 106 notifyAll()

0 comments on commit 37707cd

Please sign in to comment.
Something went wrong with that request. Please try again.