-
Notifications
You must be signed in to change notification settings - Fork 795
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
“Check for plain object” may be have a problem #114
Comments
is that really a problem? |
The second "like in browser" will slow down the code as You should not yield anything else than a Promise, a |
This one should fail if someone creates a constructor like this:
Because |
@wilmoore , no, it will not fail, as |
OH, cool. Well, that's fine then. |
@juliangruber @yanickrochon if the If i want to yield a object through a constructor(eg. ps. Actually, |
"If it ain't broke don't fix it" Is there a use case where this fails? |
yielding non-plain objects would be pretty weird and likely break in most cases, it's a pretty questionable feature in the first place haha, handy, but questionable |
how about:
or like in browser:
The text was updated successfully, but these errors were encountered: