Should the old Breaks be deprecated now there is boundary

[bishabosha]

Compiler version

3.7.1

Minimized example

import scala.util.boundary
import scala.util.control.Breaks.break

def foo(x: Int) = boundary:
  if x < 0 then break()
  else println("positive")

@main def Test = foo(-1)

Output

exception thrown when calling main method

scala.util.control.BreakControl

Expectation

If you wrote this program with an IDE that automatically inserted break, perhaps you wouldn't check why it doesn't work (i.e. perhaps not realising that you imported the old library based solution of Scala 2.13)

[som-snytt]

A linter could warn if old-style break is used when a given Label is available. Alternatively, tweak old-style break to take an erased NotGiven.

[Gedochao]

Hey, we've discussed this on this week's Scala Core meeting.
It seems we should deprecate it, but not before Scala 3.10 (so one minor after the new LTS is out).