All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

The Debate Over Explicit vs Implicit Handles in Rust Programming

By

emschwartz

7mo ago· 11 min readenInsight

Summary

This article discusses the ongoing debate in Rust programming about whether developers should explicitly invoke handle/clone operations for reference-counted values. The author examines both sides: Dioxus argues against explicit handles for high-level GUI applications where such calls are considered 'pure noise,' while acknowledging that for many applications, explicit handles are crucial for performance, memory usage, and correctness. The piece explores how to reconcile these opposing viewpoints in Rust development.

Key quotes

· 4 pulled
For the kind of high-level GUI applications they are building, having to call cx.handle() to clone a ref-counted value is pure noise.
For a lot of Rust apps, even cloning a string or a vector is no big deal.
For a lot of applications, the answer is definitely yes – knowing where handles are created can impact performance, memory usage, and even correctness.
This whole 'Ergonomic RC' work was originally proposed by Dioxus and their answer is simple: definitely not.
Snippet from the RSS feed
Continuing my discussion on Ergonomic RC, I want to focus on the core question: should users have to explicitly invoke handle/clone, or not? This whole “Ergonomic RC” work was originally proposed by Dioxus and their answer is simple: definitely not. For t

You might also wanna read