March 01 Re: First Draft: cast(ref T)... as shorthand for *cast(T*)&... | ||||
|---|---|---|---|---|
| ||||
 Posted in reply to Walter Bright | On Monday, 20 January 2025 at 23:11:46 UTC, Walter Bright wrote:
> On 1/20/2025 2:07 AM, Juraj wrote:
>> We now have local `ref`, and that makes this syntax a cognitive burden.
>
> Think of `cast(ref int)f` as "refer to `f` as if it were an `int`" and it will make perfect sense.
Why not `cast(*ref int)f`?
| |||
March 03 Re: First Draft: cast(ref T)... as shorthand for *cast(T*)&... | ||||
|---|---|---|---|---|
| ||||
 Posted in reply to Elias Batek (0xEAB) | On Saturday, 1 March 2025 at 04:21:07 UTC, Elias Batek (0xEAB) wrote:
> On Monday, 20 January 2025 at 23:11:46 UTC, Walter Bright wrote:
>> On 1/20/2025 2:07 AM, Juraj wrote:
>>> We now have local `ref`, and that makes this syntax a cognitive burden.
>>
>> Think of `cast(ref int)f` as "refer to `f` as if it were an `int`" and it will make perfect sense.
>
> Why not `cast(*ref int)f`?
What does the * signify there? f is not a pointer.
| |||
March 04 Re: First Draft: cast(ref T)... as shorthand for *cast(T*)&... | ||||
|---|---|---|---|---|
| ||||
Posted in reply to FeepingCreature | On Monday, 3 March 2025 at 09:37:57 UTC, FeepingCreature wrote:
> What does the * signify there? f is not a pointer.
That the result is of the expression is not a `ref` either.
| |||
March 10 Re: First Draft: cast(ref T)... as shorthand for *cast(T*)&... | ||||
|---|---|---|---|---|
| ||||
 Posted in reply to Dukc | On Tuesday, 25 February 2025 at 12:46:53 UTC, Dukc wrote: >If anything, we want a library helper function like Paul suggested, but I'm slightly reserved even about that. When doing reinterpret casts, it's extremely important to understand exactly how the cast works. Any abstraction over that always tends to more or less hide it. Looks like an abstraction got added: | |||
Permalink
Reply
