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

Introduce maybe parse op #761

Merged
merged 2 commits into from
Jan 14, 2025
Merged

Introduce maybe parse op #761

merged 2 commits into from
Jan 14, 2025

Conversation

xlauko
Copy link
Member

@xlauko xlauko commented Jan 14, 2025

This operation is to denote places where we are not able to determine
whether the operation is parsing or not just from local analysis.

This is to be refined in future passes or can be used as overapproximation of parser.

@xlauko xlauko added the parser label Jan 14, 2025
@xlauko xlauko requested a review from Jezurko January 14, 2025 12:41
@xlauko xlauko self-assigned this Jan 14, 2025
Copy link
Contributor

Cpp-Linter Report ⚠️

Some files did not pass the configured checks!

clang-format (v19.1.1) reports: 1 file(s) not formatted
  • lib/vast/Conversion/Parser/ToParser.cpp

Have any feedback or feature suggestions? Share it here.

@xlauko xlauko merged commit e9b159c into master Jan 14, 2025
8 checks passed
@xlauko xlauko deleted the xlauko/maybe-parse-ops branch January 14, 2025 12:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants