# What is the intended scope of \`TypeEgal\`'s exposure?

**URL:** <https://discourse.julialang.org/t/what-is-the-intended-scope-of-typeegal-s-exposure/140194>\
**Category:** Internals & Design\
**Tags:** question\
**Created:** [October 24, 2026, 1:04am UTC](https://discourse.julialang.org/t/what-is-the-intended-scope-of-typeegal-s-exposure/140194 "2026-10-24T01:04:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kimikage](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kimikage/32/14534_2.png) [@kimikage](https://discourse.julialang.org/u/kimikage)\
**Post date:** [October 24, 2026, 1:04am UTC](https://discourse.julialang.org/t/what-is-the-intended-scope-of-typeegal-s-exposure/140194/1 "2026-10-24T01:04:22Z")

</div>

Julia 1.14.0-alpha1 has been released, so I’d like to ask a question.  
Starting with Julia 1.14, end-users will easily encounter `TypeEgal`.

```julia
julia> VERSION
v"1.14.0-alpha1"

julia> zero(String)
ERROR: MethodError: no method matching zero(::Core.TypeEgal{String})
The function `zero` exists, but no method is defined for this combination of argument types.
[...]

```

While this is a minor issue compared to the benefits of `TypeEgal`, is it definitely intended behavior for `TypeEgal` to appear in the error message?  
AFAIK, there’s any explanation of `TypeEgal` for end-users for now.

Here are some more practical questions:

- Is there a possibility that the error messages will change between now and the release of v1.14.0?
- What are the best practices for doctests involving `TypeEgal`?
- Should package developers be held accountable for `TypeEgal`?