# Analysis of Elm core issues and patches

**URL:** <https://discourse.elm-lang.org/t/analysis-of-elm-core-issues-and-patches/7941>\
**Category:** Show and Tell\
**Created:** [November 26, 2021, 5:34pm UTC](https://discourse.elm-lang.org/t/analysis-of-elm-core-issues-and-patches/7941 "2021-11-26T17:34:14Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![malaire](https://avatars.discourse-cdn.com/v4/letter/m/b782af/32.png) [@malaire](https://discourse.elm-lang.org/u/malaire)\
**Post date:** [November 28, 2021, 4:35am UTC](https://discourse.elm-lang.org/t/analysis-of-elm-core-issues-and-patches/7941/6 "2021-11-28T04:35:26Z")

</div>

> [@rupert](#):
>
> This one is a good example of that; is not allowing `4.` to parse as an Int a bug or a feature?

You could ask if that is bug or feature, but what about `4d` parsing as Int but `4e` not? It’s quite hard to argue that not allowing `e` is a feature.

> <https://github.com/elm/parser/issues/28>
>
> \`int\` parser fails to parse \`42efg\` while parsing \`42abc\` works.
> ellie: https:/…/ellie-app.com/4jqm8pFGXyLa1
> 
> Related issues: https://github.com/elm/parser/issues/14 and https://github.com/elm/parser/issues/25

---

_[View the full topic](https://discourse.elm-lang.org/t/analysis-of-elm-core-issues-and-patches/7941)._