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

Explain more why pragma is the best fit #9

Closed
domenic opened this issue May 24, 2018 · 1 comment
Closed

Explain more why pragma is the best fit #9

domenic opened this issue May 24, 2018 · 1 comment

Comments

@domenic
Copy link
Member

domenic commented May 24, 2018

@erights, @mikesamuel, and @waldemarhorwat all had points I will try to jot down:

  • Pragmas offer a unique syntactic space in that they are lexical and they are backward-compatible
  • Tooling (e.g. an inliner) that wants to treat censored functions differently requires lexical source code information, not runtime information. (Compare to .censor() alternative.)
  • ... I forget Waldemar's point :(
@mikesamuel
Copy link
Member

+1

I would like to avoid inliners having to use heuristics to decide whether they can inline a call to a potentially censored function into a potentially uncensored function's body.

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

No branches or pull requests

2 participants