# Tides of Revival - Zig Feedback

**URL:** <https://ziggit.dev/t/tides-of-revival-zig-feedback/14663>\
**Category:** Explain\
**Tags:** language, game\
**Created:** [March 19, 2026, 8:05am UTC](https://ziggit.dev/t/tides-of-revival-zig-feedback/14663 "2026-03-19T08:05:19Z")\
**Posts on this page:** 1\
**Showing post:** 41

<div class="post-metadata">

**Author:** ![Luke](https://ziggit.dev/letter_avatar_proxy/v4/letter/l/7ab992/32.png) [@Luke](https://ziggit.dev/u/Luke)\
**Post date:** [March 26, 2026, 4:00pm UTC](https://ziggit.dev/t/tides-of-revival-zig-feedback/14663/41 "2026-03-26T16:00:46Z")

</div>

> No 😉 It’s just as frustrating as always, because it’s a lot of line noise for something that disolves into “nothing” in the compiler output (e.g. at that point, it would be less work to write assembly code).

+1

> [@floooh](#):
>
> PS: I still have that old idea running around in my head that a modern and ‘explicit’ language should only have a single sign-agnostic 64-bit integer type for variables (e.g. similar to CPU registers), and explicit-width and signed-vs-unsigned integer types only for storage locations (e.g. structs mapped to memory). There’s a vast unexplored region of languages that sit below C and above assembly code 😉

Before going to some extremes, I think [it was mentioned](https://ziggit.dev/t/short-math-notation-casting-clarity-of-math-expressions/10008) that there are already some simplifications that could be done to ease up the burden of dealing with numbers.

- Eliminate @floatFromInt and allowing automatic coercion of integers to floats.
- Eliminate @intFromFloat with `@ceil`, `@floor`, `@trunc` and `@round` to coerce to integer values.
- Allow operation between floats and small integer types ([https://codeberg.org/ziglang/zig/pulls/30921](https://codeberg.org/ziglang/zig/pulls/30921))

Probably some others.

---

_[View the full topic](https://ziggit.dev/t/tides-of-revival-zig-feedback/14663)._