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

potential runtime exceptions #377

Open
rtfeldman opened this Issue Aug 29, 2015 · 0 comments

Comments

Projects
None yet
2 participants
@rtfeldman
Member

rtfeldman commented Aug 29, 2015

Runtime exceptions fixable by design changes to core

#909 1 % 0 intentionally throws a runtime exception
#378 Malformed regular expressions
#381 Signal.mergeMany []

Runtime exceptions fixable by core bugfixes

#811 Json.Encode with "ctor" and ==
#723 certain Debug.toString inputs
#399 Array.slice beyond the end for Arrays with length 32 or more
#183 toString Json.Encode.null
#294 Json.Encode.null == Json.Encode.object [] (and other comparisons of null with non-null)
#177 Broken eq on some unicode strings

Runtime exceptions from packages outside core

https://github.com/elm-lang/virtual-dom/issues/106 invalid DOM attributes

Runtime exceptions from compiler issues

elm/compiler#1145 calling == on two functions
elm/compiler#1570 duplicate record fields in strict mode
elm/compiler#1559 union type constructor with . in it
elm/compiler#1574 calling _Tuple directly
elm/compiler#1516 valid recursion

Runtime exceptions that should continue to exist

  • Debug.crash - intentionally causes runtime exceptions, so shouldn't change
  • Infinite recursion/stack overflow - this is a Comp Sci problem, not an Elm problem

@evancz evancz added the meta label Aug 30, 2015

@evancz evancz changed the title from Meta issue: issues involving potential runtime errors to potential runtime errors Jun 25, 2016

@rtfeldman rtfeldman changed the title from potential runtime errors to potential runtime exceptions Mar 29, 2017

@elm elm deleted a comment from gogocurtis May 22, 2018

@elm elm locked and limited conversation to collaborators May 22, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.