Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle one simple case of resolving list of += values which #783

Closed
wants to merge 1 commit into from

Conversation

Dkhusainov
Copy link

Fixes #729 and significantly improves parsing of configs which have many += array concatenations(large play application with many play.modules.enabled, for example)

…n up to 350x speedup in one specific case and fixes StackOverFlowError
@lightbend-cla-validator
Copy link
Collaborator

return resolveSubstitutions(this, stack, context, source);
}

/**
* Optimize loading of large configs with many += array builders:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good to add a test case with a problematic example

@ennru
Copy link
Member

ennru commented Jul 6, 2023

We do not intend to extend the functionality of "Typesafe Config" further.
See https://github.com/lightbend/config#maintained-by

@ennru ennru closed this Jul 6, 2023
@tmccombs
Copy link

@ennru Does fixing bugs fall under "extend functionality"?

@ennru
Copy link
Member

ennru commented Nov 29, 2023

Does fixing bugs fall under "extend functionality"?

It may be hard to draw the line where bugs end and new functionality starts. We want to be very conservative not to change things that worked in a certain way, even if some may agree the way it worked is wrong.

@tmccombs
Copy link

I agree with that in general. But to me at least, "stack overflow on valid input" is very far on the bug side. I guess if you want to draw that line so far back that not even crashing the JVM is considered a bug, that is your choice. Although, it does make me a little sad, since I think that hocon is a great configuration language.

And I'm glad that I found this before putting the effort into trying to put together a PR to fix #800 (which is probably related to this).

@tmccombs
Copy link

Also, I totally understand that there aren't a lot of resources available to continue work on this library. And I appreciate the work that you have put into this project. I just want to understand better what exactly is meant by "feature complete", so I can know if it is worth my time to submit pull requests to fix things that I consider to be bugs.

@ennru
Copy link
Member

ennru commented Nov 30, 2023

I bulk closed PRs at the time as we want to be clear that Typesafe Config is not to evolve further. If you are up for it, I agree that this is something that would be worth fixing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

StackOverflowError when using the concatenation operator
5 participants