Skip to content

⚡ Bolt: Hoist regex compilation in LaTeX escape function#496

Closed
aafre wants to merge 1 commit into
mainfrom
bolt-regex-compilation-12831502125783268877
Closed

⚡ Bolt: Hoist regex compilation in LaTeX escape function#496
aafre wants to merge 1 commit into
mainfrom
bolt-regex-compilation-12831502125783268877

Conversation

@aafre
Copy link
Copy Markdown
Owner

@aafre aafre commented Apr 25, 2026

What

Hoist latex_special_chars mapping and regex compilation re.compile to module-level constants LATEX_SPECIAL_CHARS and LATEX_ESCAPE_PATTERN in app.py and resume_generator_latex.py.

Why

The _escape_latex function is called recursively or in loops when generating resumes. Compiling the regex pattern and creating the dictionary inside the function causes these expensive objects to be recreated on every call, which is a performance bottleneck.

Impact

Significantly reduces the overhead of _escape_latex function calls, improving performance when generating LaTeX content by eliminating repeated regex compilation.

Measurement

This optimization can be measured by comparing the execution time of rendering a large text block with many special characters before and after the change.


PR created automatically by Jules for task 12831502125783268877 started by @aafre

Co-authored-by: aafre <8656674+aafre@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request optimizes LaTeX character escaping by hoisting regex compilation and mapping dictionaries to module-level constants in app.py and resume_generator_latex.py. It also includes extensive import reorganization, code formatting for consistency, and documentation of the optimization pattern. A review comment identifies a potential issue in resume_generator_latex.py where importing from the main app module might trigger unintended side effects during standalone execution.

Comment thread resume_generator_latex.py
if not contact_info.get("linkedin_display"):
# Import the function from the same module if it exists, or use simple fallback
try:
from app import generate_linkedin_display_text
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

Importing from the main application module app.py within this utility script can trigger unwanted side effects, such as initializing the Flask application, configuring logging, and starting thread pools. This is particularly problematic when resume_generator_latex.py is used as a standalone tool. Per repository guidelines, for standalone scripts, it is preferred to duplicate logic rather than importing from a main application module to avoid these side effects.

References
  1. For standalone scripts, prefer duplicating logic over importing from a main application module if the import introduces unwanted side effects like app initialization or service connections.

@aafre
Copy link
Copy Markdown
Owner Author

aafre commented May 25, 2026

Closing duplicate — the most recent version of this change is PR #542.

@aafre aafre closed this May 25, 2026
@google-labs-jules
Copy link
Copy Markdown
Contributor

Closing duplicate — the most recent version of this change is PR #542.

Understood. Acknowledging that this work is now obsolete and stopping work on this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant