Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

<@U0N6C2Q9F>: you can pass scalac options to zinc via zinc?

...but i think the answer is that yes, you can pass environment variables to zinc via nailgun

I want my custom zinc to add some additional scalac options when it invokes the compiler. I would like to avoid doing it via pants.ini because it triggers a rebuild of 500 targets in my case

and also -S-Ycheck:typer fails on perfectly fine code

and so there are some options that I can only apply to the code slaying the compiler

unfortunately we don't currently have a way to pass options for just a single target.

but that would be super handy. cc <@U0D40NYVA>

last discussed in the context of 'fatal_warnings'

...although you could totally hack fatal_warnings to do this, hah.

change the config variables that define what fatal_warnings mean, and then pass `fatal_warnings=True` for the tasrget

<@U0N6C2Q9F>: ...apparently the actual args for fatal warnings are hardcoded... sigh. but if you edit <https://github.com/pantsbuild/pants/blob/master/src/python/pants/backend/jvm/tasks/jvm_compile/zinc/zinc_compile.py#L299>

...and then pass fatal_warnings for the target, you will have set an option only for that target.

and I can edit the python directly in the pants venv

<@U0D40NYVA>: ^ usecase for configurable "options sets"

rather than something like `fatal_warnings`

so fatal_warnings=True is passed to the target in the BUILD file?

yea... that would enable whatever args you have configured there

`scala_library(name='blah', sources=.., fatal_warnings=True)`

<@U06A03HV1>: yeah that deprecation ticket the other day kinda made me want to add a warn_deprecation flag, but that's maybe getting crazy

<@U0D9ZAH98>: Can <https://rbcommons.com/s/twitter/r/3477/> be submitted?  I want to cut a release today and its not in yet.

he might be asleep, but i expect the answer is yes.