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

Investigate replacements for boost Format for diagnostics #4784

Open
vlstill opened this issue Jul 4, 2024 · 1 comment
Open

Investigate replacements for boost Format for diagnostics #4784

vlstill opened this issue Jul 4, 2024 · 1 comment
Labels
breaking-change This change may break assumptions of compiler back ends. core Topics concerning the core segments of the compiler (frontend, midend, parser)

Comments

@vlstill
Copy link
Contributor

vlstill commented Jul 4, 2024

This was discussed in #4347 (comment).

Summary is that boost is problematic by itself and replacing boost::format is one of the critical steps to getting rid of it. One possibility would be to use fmt and later std::format.

The biggest problem with this is that other formatter will likely use a different syntax for placeholders, which would require all diagnostics (including in downstream projects) to be rewritten and this change would be quite hard to check as mistakes in placeholders would lead to runtime failures.

@vlstill vlstill added core Topics concerning the core segments of the compiler (frontend, midend, parser) breaking-change This change may break assumptions of compiler back ends. labels Jul 4, 2024
@fruffy
Copy link
Collaborator

fruffy commented Jul 11, 2024

Related: #3898

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change This change may break assumptions of compiler back ends. core Topics concerning the core segments of the compiler (frontend, midend, parser)
Projects
None yet
Development

No branches or pull requests

2 participants