tc39 proposal-function-implementation-hiding issues

tc39 / proposal-function-implementation-hiding

JavaScript language proposal: function implementation hiding

https://ci.tc39.es/preview/tc39/ecma262/pull/1739

MIT License

98 stars 7 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Explain how hiding will actually work

#52 FrameMuse opened 10 months ago
5
A possible syntax form

#51 jithujoshyjy opened 1 year ago
1
Opinion: this will cause lot of "mystery bugs" in Sentry-style applications

#50 Jabher opened 2 years ago
35
Function source text serialization in error messages

#49 bathos opened 2 years ago
5
When would these directive get used?

#48 theScottyJam closed 3 years ago
10
Semantics of top-level directive

#47 Huxpro opened 3 years ago
1
Provide a way to determine native implementations

#46 ghost closed 3 years ago
4
should non-simple parameter lists be allowed to mix with these new directives?

#45 michaelficarra opened 4 years ago
2
ecosystem consideration: JS self-profiling API

#44 michaelficarra opened 4 years ago
0
Hiding implementation of classes breaks the `is‑callable` package

#43 ExE-Boss opened 4 years ago
5
Should "show source" be part of this proposal?

#42 tmikov opened 4 years ago
6
What's the behavior of nested function?

#41 hax opened 4 years ago
4
Examples of stack position information restricting refactoring

#40 misterdjules opened 4 years ago
12
Clarification on stack frames revealing confidential information

#39 misterdjules closed 4 years ago
4
high-fidelity polyfill use case seems to impact error stack traces

#38 misterdjules closed 4 years ago
2
Clarification on the use case of protecting against callers inspecting functions' parameter names

#37 misterdjules opened 4 years ago
9
GetDirectiveContext broken?

#36 waldemarhorwat closed 4 years ago
2
Requesting more details on the motiviation for two directives

#35 codehag opened 4 years ago
4
What if it will be used by malicious code injected by browser extension or XSS?

#34 JustFly1984 closed 4 years ago
6
The behavior of ‘sensitive‘ on `Error.p.stack`

#33 lidongjies closed 4 years ago
5
add note that a follow-on proposal may add "preserve implementation" directive

#32 michaelficarra closed 4 years ago
1
enumerate security properties guaranteed by the "sensitive" directive

#31 michaelficarra closed 4 years ago
1
Appendix statement untrue for some engines

#30 erights closed 4 years ago
5
Editorial: Fixed a typographical error in README

#29 Kriyszig closed 4 years ago
0
Implementation of unhandled rejection/uncaught exception logging in Node.js

#28 misterdjules closed 4 years ago
6
Impact on observability tools relying on stack traces

#27 misterdjules opened 4 years ago
7
shouldn't this proposal be dependent of the error stacks proposal?

#26 ghermeto closed 5 years ago
4
Ability to disable the directive

#25 ghermeto opened 5 years ago
16
change the "website" URL for the repo

#24 michaelficarra closed 5 years ago
1
reconciling the disparate function implementation hiding use cases

#23 michaelficarra closed 4 years ago
2
Spell out stack hiding in more detail / maybe align with built-ins

#22 domenic closed 4 years ago
4
Class-body directive prologue is incompatible with class fields

#21 domenic closed 4 years ago
18
Interaction with other proposals and use cases

#20 dead-claudia closed 5 years ago
4
State clearly that devtools UX is out of scope

#19 domenic closed 5 years ago
0
Consider a different name besides "censorship"

#18 domenic closed 5 years ago
0
combine F.p.toString and E.p.stack censorship proposals

#17 michaelficarra closed 5 years ago
5
Censoring code should only be possible for native code, not userland code

#16 getify closed 5 years ago
32
Why describe censored code as "[native code]"?

#15 garvank closed 4 years ago
3
Update README.md

#14 techeverri closed 5 years ago
0
Decorator-like syntax suggestion

#13 littledan closed 4 years ago
15
Why not censor all functions, or at least cross‑module functions?

#12 ExE-Boss closed 6 years ago
3
This pragma is *very* long...

#11 dead-claudia closed 6 years ago
1
Explain why we think this won't become boilerplate in every source file

#10 domenic closed 5 years ago
4
Explain more why pragma is the best fit

#9 domenic closed 5 years ago
1
Interaction with stacks?

#8 ljharb closed 5 years ago
10
More info regarding the difficulties involved in "cloning" functions

#7 spion closed 5 years ago
2
Add non-normative text clarifying what this actually does

#6 domenic closed 5 years ago
15
"Function.prototype.toString()-Censored Code" copypasta

#5 domenic closed 6 years ago
0
Motivation for pragma?

#4 littledan closed 5 years ago
5
What should the pragma be named?

#3 domenic opened 6 years ago
35