Diagnostics for incorrect enum members order, when enum entry follows enum member. A few diagnostic tests.

Now incorrect enum members order is treated as a warning.
This commit is contained in:
Mikhail Glukhikh
2015-05-14 15:55:51 +03:00
parent 983339e1c9
commit 4e1a90ee61
14 changed files with 351 additions and 47 deletions
@@ -0,0 +1,9 @@
enum class MixedEnum {
<!ENUM_ENTRY_USES_DEPRECATED_OR_NO_DELIMITER!>ENTRY1<!>,
companion object {
val first = 1
}
<!ENUM_ENTRY_USES_DEPRECATED_OR_NO_DELIMITER, ENUM_ENTRY_AFTER_ENUM_MEMBER!>ENTRY2<!>,
fun foo(): String = "xyz"
<!ENUM_ENTRY_AFTER_ENUM_MEMBER!>ENTRY3<!>
}