Updates and remove redundant settings #101
Conversation
keynmol
commented
Feb 13, 2025
keynmol
commented
- Update versions (scala 3 lts, native version)
- Remove redundant native config settings – not only were the comments and values out of sync, but I think it's best to provide a minimal config relying on defaults.
- Enable source level debugging – for nicer stacktraces and debug information.
- Use Scala 3 syntax
| @@ -10,7 +10,7 @@ import scala.scalanative.build._ | |||
|
|
|||
| // defaults set with common options shown | |||
| nativeConfig ~= { c => | |||
| c.withLTO(LTO.none) // thin | |||
There was a problem hiding this comment.
These were here to help people with these basic settings (using the defaults) with some suggestions in the comments for settings you might want to select - maybe the comments where not explained well but that was deliberate as the first thing people asked for was how to optimize and such.
| @@ -1 +1 @@ | |||
| sbt.version = 1.10.6 | |||
| sbt.version = 1.10.7 | |||
There was a problem hiding this comment.
I believe that a later PR (perhaps #109) has superseded this change.
| @@ -1,4 +1,4 @@ | |||
| scalaVersion := "3.3.3" // A Long Term Support version. | |||
| scalaVersion := "3.3.5" // A Long Term Support version. | |||
There was a problem hiding this comment.
A timely & positive edit when created but Overcome By Events: PR #109.
| @@ -1 +1 @@ | |||
| sbt.version = 1.10.6 | |||
| sbt.version = 1.10.7 | |||
| @@ -1 +1 @@ | |||
| addSbtPlugin("org.scala-native" % "sbt-scala-native" % "0.5.1") | |||
| addSbtPlugin("org.scala-native" % "sbt-scala-native" % "0.5.6") | |||
There was a problem hiding this comment.
A merciful and well needed update at the time of creation but
now superseded. I believe the current template uses 0.5.8.
| def main(args: Array[String]): Unit = | ||
| println("Hello, world!") | ||
| } | ||
| @main def hello = println("Hello world from Scala Native!") |
There was a problem hiding this comment.
I, for one, like this change and would like to see it proceed.
Not an earth shaking changes, but I have "Hello world", of various
flavors, popping into my log files all over the place. Always nice to
know who is speaking, just like radio protocol.
There was a problem hiding this comment.
I think there was none lto because it was failing on the Mac. As long as we have a NativeConfig so the user doesn't have to figure out that ceremony I am good.
| c.withLTO(LTO.none) // thin | ||
| .withMode(Mode.debug) // releaseFast | ||
| .withGC(GC.immix) // commix | ||
| c.withSourceLevelDebuggingConfig( |
There was a problem hiding this comment.
Perhaps the current nativeConfig section, with the alternatives
can be preserved and the right hand comment changed to something
like "// frequent alternative 'foo'".
The problem with minimalism, especially for people just joining the party, is the balance between how may people a comment gains and how many people it looses/confuses. I'd ask to be given Wisdom but
I am afraid that is something that must be earned.
As one voice among many, I like having that section, with some alternatives and use both it and the alternative quick reference all the time "now, once again, is that releaseFast or release-fast?"
| .withMode(Mode.debug) // releaseFast | ||
| .withGC(GC.immix) // commix | ||
| c.withSourceLevelDebuggingConfig( | ||
| SourceLevelDebuggingConfig.enabled |
There was a problem hiding this comment.
I've never used this feature. What does it do?
What is it's overhead? Does it need to be backed off or
output stripped for an application release?
Since it is non-default, perhaps it could be put either as a comment
block stating that developers find it useful, with a link to the
section in the "User's Guide".
Another alternative would be, if overhead in eventual binary is low,
to have another code block which either enables it or shows it
as the default disabled and suggests, as a step beyond "Getting Started" that one read the URL link and enable it.
I think that Eric formulated the idea of having a README of links
to more advanced .g8 templates actually used by experienced developers. Perhaps we could salt it with an "Once you have gotten started" intermediate template (perhaps showing C "-v" verbose options or such.)
There was a problem hiding this comment.
Folks, Where do we go from here?
I am hoping that "Hell in a handbasket" is not one of the suggestions.
Thanks,
Lee
There was a problem hiding this comment.
I am hoping that "Hell in a handbasket" is not one of the suggestions.
Must be getting late there. :-)
There was a problem hiding this comment.
I used to (attempt to) teach young adults. They taught me to never ask an
open ended question if you were not willing to accept all answers offered ;-)
|
Totally agree but in this case I am not picky - Wanted to give them a template with the defaults and hints on what they may need - when everything is new even basic settings are what? huh? And then Anton adds the source debugging which is probably worth a Master's thesis. |
|
Riffing off what you said. Perhaps something like:
I think folks can wordsmith the right hand part until the cows come home and into |
