Submitting a JEP
brian.goetz at oracle.com
Fri Oct 6 03:17:28 UTC 2017
The proposal is a bad fit for the assertion facility, since the
assertion facility is designed to be disabled, and what you want is
something that can't be disabled.
But here's an alternative:
throw new UnreachableAssertionException("why");
This doesn't need a language feature. It doesn't even need a special
throw new AssertionError("Unreachable: blah blah");
Adding language features has a significant cost; we prefer to spend that
where there are not practical alternatives.
On 10/5/2017 5:27 PM, Daniel Trebbien wrote:
> I have an idea for enhancing the Java programming language (
> https://github.com/dtrebbien/JEP-Unreachable-Assertions ). It is my
> understanding that in order to change the Java programming language, a JSR
> will need to be written, but that a good first step is to submit a JDK
> Enhancement Proposal to gauge support for the idea. I read JEP 1: JDK
> Enhancement-Proposal & Roadmap Process (http://openjdk.java.net/jeps/1 )
> and followed the instructions: I wrote a draft JEP using the template (
> http://openjdk.java.net/jeps/2 ) and emailed my Markdown file to "jep dash
> submit at openjdk dot java dot net", converted back to a valid email
> That was five days ago and I have not received a response. It could very
> well be that people are busy. I would like to confirm, though, that the
> emailing procedure is still used now that JEPs are being migrated to the
> JDK Bug System (http://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html ).
> Is "jep dash submit at openjdk dot java dot net" actively monitored?
More information about the discuss