You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 25, 2025. It is now read-only.
Probably a nit but it seems like "arg" might be the wrong term. Perhaps it should be something more generic like at. at also has the upside of working nicely with anything that takes a list in the DOM.
Since it seems silly to make a new issue for something so small but perhaps we should throw a RangeError instead of a TypeError if the requested index out of bounds?
The text was updated successfully, but these errors were encountered:
Actually, I think I was misreading the JS spec. They are arguments and not results in the WASM Signature. That said, I think the other questions are still valid.
I'm not sure what you mean by "working nicely with anything that takes a list in the DOM" - you need to pass the tag, so it's not like you can treat it as a list directly.
I guess I don't see either change as much of an improvement, but I don't care deeply either way.
Probably a nit but it seems like "arg" might be the wrong term. Perhaps it should be something more generic like
at
.at
also has the upside of working nicely with anything that takes a list in the DOM.Since it seems silly to make a new issue for something so small but perhaps we should throw a
RangeError
instead of aTypeError
if the requested index out of bounds?The text was updated successfully, but these errors were encountered: