NotImplementedException should give a compile-time warning

[DartBot]

This issue was originally filed by jeffbailey@google.com

---

What steps will reproduce the problem?

1. Try to use textWindow.nodes.removeRange(1, 1);
2. Get runtime NotImplementedException
   3.

What is the expected output? What do you see instead?

I get a clean compile but a runtime failure. I expect compile time notification if there's something the system can know will be a problem in advance.

What version of the product are you using? On what operating system?

Path: .
URL: http://dart.googlecode.com/svn/branches/bleeding_edge/dart
Repository Root: http://dart.googlecode.com/svn
Repository UUID: 260f80e4-7a28-3924-810f-c04153c831b5
Revision: 1856
Node Kind: directory
Schedule: normal
Last Changed Author: floitsch@google.com
Last Changed Rev: 1856
Last Changed Date: 2011-11-25 08:03:42 -0800 (Fri, 25 Nov 2011)

Please provide any additional information below.

[DartBot]

This comment was originally written by drfibonacci@google.com

---

Added Area-Frog, Triaged labels.

[DartBot]

This comment was originally written by jeffbailey@google.com

[jmesserly]

The tricky part is the system doesn't know it will throw that exception--this is just coming from the method itself, which reads "removeRange(int start, int length) { throw const NotImplementedException(); }". In general in you can't figure out which method will be called (if types are omitted).

Assuming it's fully typed, though, we could add a special check for "throw const NotImplemenentedException();" and issue a warning.

---

Removed Priority-Medium label.
Added Priority-Low label.

[DartBot]

This comment was originally written by mattsh@google.com

---

This is by design. While code is being worked on and not yet finished, it's useful to have a way to stub out methods that aren't yet implemented in order to avoid getting compile warnings/errors. If the compiler gave warnings/errors when it saw NotImplementedException, that would defeat the purpose.

---

Added WontFix label.