Announcing Rust 1.28
I&#x27;ve been studying Rust on and off in the past 3 months. There are a few things that I find annoying, they are somehow discussed in the issue tracker, but it&#x27;s not clear to me what the priorities are to land them:<p>* Partial borrow. I can&#x27;t borrow a field of a structure and then reference another field. I can&#x27;t cite how many times in a few weeks I&#x27;ve been forced to rethink and split my structures just to work around this, making my code harder to read and write for no good reason than working around this limit of the borrow checker.<p>* The Rc&#x2F;RefCell&#x2F;Box dance is very verbose, when you just want to share a reference to some long-living object within other long-living objects. Worse than verbose, it also causes a runtime overhead because of the RefCell.<p>* No simple way to declare non-const global objects, like something as easy as a global HashMap of constants strings to constant integers. I&#x27;m a little spoiled from Go&#x27;s excellent support of init functions (both compiler-generated and manually written), but this is something I really miss in Rust. lazy_static! is a workaround which is harder to use and forces the code to be thread-safe even if no threading support is necessary (that is, I can&#x27;t use my non-thread-safe classes in a lazy_static).<p>* In generic code, there is no simple way to represent integer types. You need to use the &quot;num&quot; trait which breaks the &quot;as&quot; operator causing big pain and less readable code (as it&#x27;s normal to covert between integer types).<p>* No integer generic parameters. We have to use the &quot;typenum&quot; crate which ends up causing less readable code and generates C++-like error messages.<p>* PhantomData is awkward, it absolutely sounds like something the compiler should handle, not the programmer.<p>* &quot;Wrapping&lt;u32&gt; + 1&quot; doesn&#x27;t compile, but is there a good reason why it does not? I really wish Rust added wuNN&#x2F;wiNN native wrapping types, or evolved in a way that I can write the same code with &quot;u32&quot; and &quot;Wrapping&lt;u32&gt;&quot; (another example: &quot;as&quot; doesn&#x27;t work). Right now, it seems like the solution is half-baked: it tries to use the generic to avoid adding a native type, but the code that users must write is more bloated compared to native types.