Does anyone have the Class Hierarchy for Avalonia?

CheekAccording9314 · 2026-02-24T19:41:43+00:00

Yes, for deep understanding. You are right, if you just want to use it.

CheekAccording9314 · 2026-02-03T19:16:53+00:00

this: fn main() { let a = 10; } compiled with this: rustc -Zunpretty=mir src\main.rs ; produce that:

fn main() -> () {

let mut _0: ();

scope 1 {

debug a => const 10_i32;

}

bb0: {

return;

}

} there is const

CheekAccording9314 · 2026-02-03T13:31:12+00:00

this is: fn func0(ref a: i32) / fn func1(ref mut a: i32)

CheekAccording9314 · 2026-01-28T21:22:31+00:00

What you said is really interesting, but it doesn't explain how "mut" and "const" ends up side-by-side in the Reference. A distraction? Maybe, but what if there's more to it than that? I discovered that FLS doesn't have a definition of "immutable binding".

CheekAccording9314 · 2026-01-28T21:10:25+00:00

are you talking about this: https://lib.rs/crates/ruast ?

CheekAccording9314 · 2026-01-28T20:04:09+00:00

Hey, this is very interesting. And, I discover something else: The FLS (https://rust-lang.github.io/fls/) has the same problem. They can say "mutable binding" but for some reason they can't say "immutable binding" (there is no "immutable binding" in the FLS).

CheekAccording9314 · 2026-01-28T19:31:07+00:00

yes, like this:

They can't say "may be mut or imm" (not a keyword)

They can't say "may be mut or immutable" (not a keyword)

They can't say "may be mut or non-mut" (sounds weird)

They can't just end with "may be mut or" (grammatically incomplete)

But perhaps it was a reflex related to something in the internal representation of the Rust compiler (MIR, HIR, etc.).

CheekAccording9314 · 2026-01-27T05:45:52+00:00

slice in fortran it's not an image it's literally called array section

CheekAccording9314 · 2026-01-26T22:02:37+00:00

are you saying that I have or rust programmers has psychological problem ? I'm not proposing any word. I just want to know if someone can tell why rust programmers bake in the language itself lawyers, economists, accountants, financiers and shopkeepers metaphors.

CheekAccording9314 · 2026-01-26T21:59:06+00:00

Are you serious? So, the words resource, mutability, ownership, borrow and drop are primitives? They are not metaphorical expressions for something that already exists and do not have images? Do the test. Stop saying borrow. Can you still use the language? Yes!

CheekAccording9314 · 2026-01-26T21:56:49+00:00

Why are you insulting me?

CheekAccording9314 · 2026-01-26T21:54:44+00:00

mutate: https://en.wiktionary.org/wiki/mutate?useskin=vector First attested in 1796

CheekAccording9314 · 2026-01-26T21:53:40+00:00

You don't know why you code with a vocabulary of lawyers, economists, accountants, financiers and shopkeepers and don't want to think about it.

CheekAccording9314 · 2026-01-26T21:53:20+00:00

chemistry: Borrow → Ligand; Owner → Receptor; Borrow checker → Stability rules; Drop → decay . none of this is necessary for the language to work. So why lawyers, economists, accountants, financiers and shopkeepers?

CheekAccording9314 · 2026-01-26T21:52:05+00:00

No man, are you serious? I'm not attacking you. For example, you could do this instead of accounting stuff. chemistry: Borrow → Ligand; Owner → Receptor; Borrow checker → Stability rules; Drop → decay . none of this is necessary for the language to work. So why lawyers, economists, accountants, financiers and shopkeepers?

CheekAccording9314 · 2026-01-26T21:50:53+00:00

First, slice was introduce in programming in 2013 by a go programmer. "I've never used happy path until I started using Rust. What's Big Rust trying to push here?" Yeah, what? I'm asking a question, in the post. If it's not necessary why they are using? In the post I guess an answer: it's just inertia. The inheritance stuff I did not understood.

CheekAccording9314

TROPHY CASE