GitHub user mdedetrich edited a comment on the discussion: Replace typesafe config for sconfig for Pekko 2.0.0
> Well, I'd prefer not to add more - could it just be in the presistence > project as a utility? The config format is another possible addition but that > could be in scalameta perhaps. My priorities are really improving the code, > test coverage, and Scala Native features such as embedded config files - this > last one seems to be a tough one. Just adding the formatting features is > challenging as explained. True, although a proper implementation would go recursively down the config ast and change each ast node to the other libraries equivalent (which is a one to one mapping). This solution would be faster and may also be more accurate if a future divergence in parsing ever occurs. GitHub link: https://github.com/apache/pekko/discussions/2186#discussioncomment-14367564 ---- This is an automatically sent email for notifications@pekko.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@pekko.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For additional commands, e-mail: notifications-h...@pekko.apache.org
