Just asking: why call them "frozen options" instead of the more common "immutable options"?

How would you handle setting default values? Should it be entirely forbidden to set a default value for frozen options?

@javiereguiluz there is no specific reason. i call it frozen because, i see isFrozen in Symfony couple times.

@xabbuh IMO, only the assigned options can be frozen. i'll make a commit for that, an option can only frozen if the default value is assigned.

Can you explain a use case for such a feature?

@unexge a frozen DIC container is not immutable. Only some mutations are forbidden

Please also open a PR to the documentation to document this new feature (and reading this doc will also help understanding the goal of this feature)

@xabbuh for me: i've options, and default values came from parameters.yml. and i want to change some of them runtime, but some of them must be stay as the default. i can use the setAllowedValues for setting allowed values only the value came from parameters.yml, but this is a hack, its better to freeze options.

@stof as you saw my typos, my english is not very well 😃. so, may be, someone help for documentation. and for naming, if immutable came more make sense, we can use immutable instead of frozen.

@unexge : Despite the mentioned use-case, I'm currently missing the point of an option you cannot configure 😕 Why even making it an option then ?

@ogizanagi for all options came from one source. so i mean;

$options = // all options

instead of

$options = // mutable options
$frozenOptions = // frozen options

So far the code looks reliable to me

@OskarStark thanks for the review, unnecessary phpdoc removed.

@unexge I am unsure if options that couldn't be configured at runtime really should be options. For example, when using the options resolver in a form type, I would rather register the form type as a service and inject the "unconfigurable options" in the constructor and I think there are similar approaches for other use cases where you would want to use frozen options.

@xabbuh you're right. it's really rarely use case the frozen an option. i'm closing the PR, thanks.

Thanks @xabbuh for succeeding into pointing out what I failed to explain 👍

BTW the only real use-case I see is an implementation wanting to lock an inherited option by providing its own value, and won't allow to change it.

I.e: Form type B inherits from form type A, set a default value for option foo, and won't allow to change foo back.