# Why does scientific notation break the range function?

**URL:** <https://discourse.julialang.org/t/why-does-scientific-notation-break-the-range-function/80014>\
**Category:** New to Julia\
**Created:** [April 25, 2022, 8:46pm UTC](https://discourse.julialang.org/t/why-does-scientific-notation-break-the-range-function/80014 "2022-04-25T20:46:57Z")\
**Posts on this page:** 1\
**Showing post:** 54

<div class="post-metadata">

**Author:** ![trahflow](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/trahflow/32/30585_2.png) [@trahflow](https://discourse.julialang.org/u/trahflow)\
**Post date:** [April 26, 2022, 5:41pm UTC](https://discourse.julialang.org/t/why-does-scientific-notation-break-the-range-function/80014/54 "2022-04-26T17:41:19Z")

</div>

Relevant issue: [better error for passing wrong type of keyword argument · Issue #29829 · JuliaLang/julia · GitHub](https://github.com/JuliaLang/julia/issues/29829)  
Seems like the function/method name used to be part of the error message, but was changed. According to a comment by Jeff on the linked issue this _should_ be part of the stack trace.  
I’m confused now 😅

Edit:  
[here](https://github.com/JuliaLang/julia/blob/master/base/errorshow.jl#L62-L84) is how the error message is formed. It has a special case for `TypeError`s from keyword arguments. This is a bit weird, but I guess there was a deeper reason for that related to above issue.

---

_[View the full topic](https://discourse.julialang.org/t/why-does-scientific-notation-break-the-range-function/80014)._