pawegio
04/21/2016, 9:22 AMyole
04/21/2016, 9:22 AMpawegio
04/21/2016, 9:23 AMyole
04/21/2016, 9:33 AMmikehearn
04/21/2016, 9:34 AMmikehearn
04/21/2016, 9:34 AMpawegio
04/21/2016, 9:40 AMmikehearn
04/21/2016, 3:54 PMdh44t
04/21/2016, 3:55 PMdh44t
04/21/2016, 3:57 PMdh44t
04/21/2016, 3:57 PMdh44t
04/21/2016, 3:57 PMorangy
mikehearn
04/21/2016, 4:32 PMmikehearn
04/21/2016, 4:33 PMmsridhar
04/21/2016, 11:00 PMyole
04/22/2016, 4:55 AMyole
04/22/2016, 4:55 AMyole
04/22/2016, 4:56 AMmsridhar
04/22/2016, 4:58 PMmsridhar
04/22/2016, 5:01 PMdamian
04/22/2016, 10:20 PMdebug
04/23/2016, 12:42 PMyole
04/23/2016, 12:56 PMdebug
04/23/2016, 1:50 PMmikehearn
04/25/2016, 9:08 AMmikehearn
04/25/2016, 9:23 AMfellshard
05/10/2016, 2:14 AMkirillrakhman
05/10/2016, 8:33 AMmartinb
05/13/2016, 2:11 PMshould we have an inspection for kotlin methods whose return type is a platform type?One of the main reasons why my Java team switched from Eclipe to IntelliJ was external annotations. We have since externally annotated `@Nonnull`/`@Nullable` on most methods in the APIs that we use. In our own source code we only use
@Nullable
, with all packages annotated with @ParametersAreNonnullByDefault
.
Neither @ParametersAreNonnullByDefault
nor external annotations works in the IntelliJ Kotlin plugin at the moment.
For @ParametersAreNonnullByDefault
there is youtrack issue KT-10942, but no indication when it will be implemented.
For external annotations, all relevant youtrack issues I could find are marked as obsolete.
These are two blocking issues before being able to start using Kotlin at my workplace.