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

not to use replacen() in ConditionCompiler.tokenize() function #1277

Closed
hach1yon opened this issue Feb 12, 2024 · 1 comment · Fixed by #1287
Closed

not to use replacen() in ConditionCompiler.tokenize() function #1277

hach1yon opened this issue Feb 12, 2024 · 1 comment · Fixed by #1287
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers
Milestone

Comments

@hach1yon
Copy link
Collaborator

This issue is a sub issue of #787 .

ConditionCompiler.tokenize() function utilizes replacen() in the while loop. A new string instance would be created in hhe function replacen() so we can reduce memory usage if we replace replacen() with something.

ConditionCompiler.tokenize() use replacen() in order to memorize how far the tokenization has progressed. I think this can be replaced with index access.

@hach1yon hach1yon added enhancement New feature or request good first issue Good for newcomers labels Feb 12, 2024
@YamatoSecurity YamatoSecurity added this to the v2.14.0 milestone Feb 27, 2024
@YamatoSecurity
Copy link
Collaborator

@fukusuket is interested in this issue so I have assigned him.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants