issues Search Results · repo:tc39/proposal-extensions language:HTML
Filter by
16 results
(99 ms)16 results
intc39/proposal-extensions (press backspace or delete to remove)I m a big fan of the idea of extension functdions and accessors. I even posited the idea for virtual accessors back on
the old bind operator proposal, so I m glad to see they made it into this one. Every ...
andyearnshaw
- 5
- Opened on Sep 26, 2024
- #17
It would be great if optional chaining was baked into the proposal:
document.querySelector( #myElement )?::let(it = {
// it s safe to do things with the element here
setupInteractivity(it);
});
...
- 4
- Opened on Sep 26, 2024
- #16
According to tc39/proposals, this proposal was last presented in November, 2020. Has there been any progress advancing
to stage 2?
Conclusion/Resolution proposal advances to stage 1 stage 1 concerns about ...
gonzojive
- 1
- Opened on Jul 27, 2024
- #15
One use case of this proposal is providing good syntax for first-class protocol:
protocol MyProtocol {
foo
bar() {
this::foo() // instead of this[MyProtocol.foo]() which is wordy and unsafe
...
hax
- Opened on Jun 2, 2022
- #14
Currently the proposal is named as Extensions and :: operator . I m considering rename it to static dispatch operator
(contrasts with . and [], which are dynamic dispatch operators).
Though extension ...
- 1
- Opened on Jun 2, 2022
- #13
Current design and the pitfalls
value::X:foo(...args) currently support both constructors and namespace objects by default.
For constructors, it works as X.prototype.foo.call(value, ...args). For namespace ...
- Opened on Jun 1, 2022
- #12
Node contains a lot of methods that are uncurry the value of this in order to safely obtain functionality like
[0, 1].slice() that is not subject to prototype pollution. This proposal would effectively ...
bmeck
- 23
- Opened on Sep 20, 2021
- #11
const ::example = { get() { console.log(1); } }
const get = function () { console.log(2); }
const cond = Math.random() 0.5;
cond ? null::example:get(); // How will this be parsed?
cond ? null::example:get() ...
MadProbe
- 4
- Opened on Mar 22, 2021
- #10
// util.js
export const toSet = iterable = new Set(iterable)
import * as util from ./util.js
[]::util:toSet();// why here equals to `util.toSet([])`, but not `util.toSet.call([])`?
If so, why not ...
LongTengDao
- 5
- Opened on Mar 8, 2021
- #9
I saw the proposal is const ::toArray=... now.
Why not const toArray=... simply, like old proposal did?
- 19
- Opened on Mar 3, 2021
- #8
Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Press the /
key to activate the search input again and adjust your query.Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Press the /
key to activate the search input again and adjust your query.