# \[RFC\] Ideas for tools around type stability / optimization

**URL:** <https://discourse.julialang.org/t/rfc-ideas-for-tools-around-type-stability-optimization/33850>\
**Category:** Tooling\
**Tags:** proposal\
**Created:** [January 27, 2020, 2:28pm UTC](https://discourse.julialang.org/t/rfc-ideas-for-tools-around-type-stability-optimization/33850 "2020-01-27T14:28:47Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![longemen3000](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/longemen3000/32/7298_2.png) [@longemen3000](https://discourse.julialang.org/u/longemen3000)\
**Post date:** [January 27, 2020, 2:48pm UTC](https://discourse.julialang.org/t/rfc-ideas-for-tools-around-type-stability-optimization/33850/2 "2020-01-27T14:48:02Z")

</div>

Related in some way:

> [@Code\_native opcode annotations](https://discourse.julialang.org/t/code-native-opcode-annotations/29562):
>
> For those of us not yet fluent in reading assembly, code\_native output could be enhanced with human-readable annotations of what the opcodes represent. This will save us from constantly searching through docs to find meanings of the more obscure opcodes. Are there any existing annotation tools? I searched and did not find anything. I’m surprised that no one already built a simple web app that annotates blobs of assembly. This doesn’t seem too difficult to introduce to Julia’s code\_native funct…

I totally support that. Maybe creating an struct that holds the info is better than raw text

---

_[View the full topic](https://discourse.julialang.org/t/rfc-ideas-for-tools-around-type-stability-optimization/33850)._