Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Blank lines slow down compilation dramatically
See original GitHub issueFragment shader gist with this issue being present. On my laptop it takes >20 sec to compile. And this is exactly the same shader, comments removed, which compiles instantly.
Also, it seems like you can’t have /*...*/ comments anywhere in your code, as it ruins commands such as /*{server:3000}*/.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Can empty lines between code lines decrease the ...
It has no effect on the compiled code. It's a good thing to use whitespace as it can greatly improve readability.
Read more >bb4w@groups.io | Empty lines slow down code?
In your experience, do empty lines slow down program execution? Not significantly, and a blank line will be slightly faster than a line ......
Read more >Do blank spaces in source code affect the performance of ...
The compiler couldn't possibly care less if you included zero or seven thousand spaces - it skips over them when it compiles the...
Read more >The Little Things: Speeding up C++ compilation
We will consider the compilation of C++ binary to happen in 3 steps: ... The first row shows the time needed to compile...
Read more >Technically speaking do comments and whitespaces slow ...
That's because Python doesn't simply interpret line by line. It will first compile the code (to bytecode), then feed it to the VM....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve updated VEDA to 2.4.2 and the issue is gone. It seems like 8d19883 fixed all this weird behaviour.
Interestingly, replacing commented code with dummy text helped a bit. Now compilation time is about 10 sec.