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

🚀 Remove NoInline compiler usages #31837

Merged
merged 9 commits into from
Jan 7, 2021

Conversation

kristoferbaxter
Copy link
Contributor

Issue #4104.

This PR removes the NoInline compiler rule since V8 has since fixed the performance of code within try/catch blocks. Bonus, this means the codebase is a bit smaller when shipped over the wire.

@amp-owners-bot amp-owners-bot bot requested a review from rsimha January 6, 2021 23:25
@kristoferbaxter kristoferbaxter changed the title 🚀 Remove NoInline compiler rule 🚀 Remove NoInline compiler usages Jan 6, 2021
@amp-bundle-size amp-bundle-size bot requested a review from samouri January 6, 2021 23:42
@@ -104,13 +104,9 @@ function compileCss(options = {}) {
*/
function writeCss(css, jsFilename, cssFilename, append) {
return toPromise(
file(
jsFilename,
'/** @noinline */ export const cssText = ' + JSON.stringify(css),
Copy link
Contributor

Choose a reason for hiding this comment

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

Nice to see the removal of the hack added by #23373.

Copy link
Contributor

@jridgewell jridgewell left a comment

Choose a reason for hiding this comment

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

There are probably a few methods called xNoInline around the codebase?

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

Successfully merging this pull request may close these issues.

5 participants