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 has been archived by the owner on Jun 12, 2019. It is now read-only.
This is a bit odd in that if enacted along with #7, would have the effect of completely swapping which functions are currently Effectful - since #7 adds Effect to parse functions, and I suggest removing it here; I couldn't find any explicit reason why new DOMParser should be effectful. The w3c docs do not seem to indicate IO or exceptions as a result of calling the constructor.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is a bit odd in that if enacted along with #7, would have the effect of completely swapping which functions are currently
Effect
ful - since #7 addsEffect
to parse functions, and I suggest removing it here; I couldn't find any explicit reason whynew DOMParser
should be effectful. The w3c docs do not seem to indicate IO or exceptions as a result of calling the constructor.The text was updated successfully, but these errors were encountered: