David Gregory

I think this behaviour is the same for java.time as well. I was a bit confused by this because on some issues it has been mentioned that the library follows...

I wonder if it would be sufficient to check `in.available() > 0` before calling `in.read()` in [SyncConsole](https://github.com/typelevel/cats-effect/blob/series/3.x/std/shared/src/main/scala/cats/effect/std/ConsoleCrossPlatform.scala#L194=)? That should at least tell us whether `read()` will block.

> what should we do in the case when `available() == 0`? ``` while (in.available() == 0) {} ``` I'm tempted to put :trollface: but I think it actually would...

This is kind of done as we now have https://github.com/typelevel/scalac-options, but I'm going to leave this open until #107 lands.

If Someone™️ wants to do the work to add a JavacOptions DSL I don't have any objection in principle, but since I rarely use mixed projects personally I wasn't planning...

At the moment there are different modes for the plugin, and default "option sets" for each mode. For the "development" mode we have: ```scala tpolecatDevModeOptions := ScalacOptions.default ``` for "CI"...

> If you want to disable fatal warnings for part of your build for whatever reason, how would you do that with sbt-tpolecat? To answer this specific question, you could...

I have a PR open with sbt to make removing options nicer (https://github.com/sbt/sbt/pull/6856) but unfortunately it's stuck on a legal review of the CLA at the moment 😢

Good places to look to understand what we need to configure here: https://docs.oracle.com/javase/8/docs/technotes/tools/windows/javac.html https://docs.oracle.com/en/java/javase/11/tools/javac.html https://docs.oracle.com/en/java/javase/17/docs/specs/man/javac.html Annoyingly the page for the javac command keeps moving in each JDK release 😆

I wonder if we can ask an sbt expert like @eed3si9n about this one? At the moment this plugin simply sets `scalacOptions` without reference to any specific scope. It seems...