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

Measure Razor performance and look for an alternative #615

Closed
smedilol opened this issue Jul 19, 2017 · 1 comment
Closed

Measure Razor performance and look for an alternative #615

smedilol opened this issue Jul 19, 2017 · 1 comment

Comments

@smedilol
Copy link
Contributor

smedilol commented Jul 19, 2017

It seems that razor is not fast enough. It generates temp files to generate skeleton.
We need to see how "fast/slow" razor really is and look for an alternative.

One possibility is to generate the code directly in C#.
Our skeletons are not complicated.

Edit: Study http://www.stringtemplate.org/

@smedilol smedilol added this to the CodeElement/Node refactoring milestone Jul 19, 2017
smedilol added a commit that referenced this issue Aug 25, 2017
So our private tests can now generate the code with our skeleton.
smedilol added a commit that referenced this issue Aug 25, 2017
Added an error counter for these Diagnostics.
smedilol added a commit that referenced this issue Aug 25, 2017
…reported as diagnostics and will not crash all codegen
@mayanje
Copy link
Contributor

mayanje commented Jan 9, 2019

Ok according to #1028, this issue is now obsolete

@maxime645 maxime645 mentioned this issue May 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants