Skip to content

Curly braces in configuration options are a source for unintentional misconfiguration #32

Closed
@MartinSpiessl

Description

@MartinSpiessl

This came up here:

https://gitlab.com/sosy-lab/software/cpachecker/-/issues/578#note_412659072

Some users use some.config.option={} in their benchmark xml and config files. However it seems to be unclear whether this (while apparently working) is actually disallowed or not. According to @PhilippWendler this will be interpreted as the literal string {} and not as an empty collection.

I guess the problem comes probably from the fact that the documentation that is generated for the configuration options lists collection-type default values in curly braces, while users are actually never supposed to add those braces (?). I created issue #31 for this.

We should probably either support curly braces in config values or emit a warning in such circumstances.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions