init properties: Do they also work for normal fields?

[msedi]

As the new init-only properties will come I came into a situation today where the question came up if they also work for fields?
So my question is if this would work? For hi-perf computing it's not always helpful to have getters and setters, so I think the situtation as shown below is quite common:

struct Point
{
  int init X;
  int init Y;
}

[YairHalberstadt]

For hi-perf computing it's not always helpful to have getters and setters

I'm interested what this case is. Usually the jit will inline pretty much all autoprops.

[msedi]

@YairHalberstadt: That's a valid argument! I haven't really tested this nowadays - lets say it has been a bottleneck years ago and I didn't follow it. I will do.

The question nevertheless is will there be some init for fields?

[YairHalberstadt]

For example these two methods produce identical jit:

https://sharplab.io/#v2:EYLgtghgzgLgpgJwDQxNMAfAAgJgIwCwAUFgAwAEWeAdAEoCuAdjAJZhzUDCA9mAA4sANogDKiAG4sAxnCgBuYsSwBmSjnKdyAb2Lk9lVVgAs5ALJ4AFAEptu/ffEQE5PtxbNyAXnKM4Ad3IABTcPLXIAfQAPL3I8JAiATxj1AF8FInt7ABUIAGtZYPcYC1ciq3T7FLs9aoNKE1Mca1sMzL1HZ1KPb18AwtDyAA0YuPIATWTyNNrsvIKQ4q6Yctqq1pr18gBtUzgYAAtuABMASX5BC12D47O+QQB5PlZuRihqADluE8ZBd3cAcysAF1aip6uQcvkoP1ijCXAsrFo1mslKpYAh6FIYEEFsQdJswUUIpEKvpCR5wglSXpydjhmF/nsvAA+YlychQJmeVlRGKOQT0ODstb2WnjbTkRnY7mJdmc6U8pLefmC4XEFJAA=

I don't believe there's any plans right now. It is a reasonable suggestion.

If you can come up with some realistic use cases I would definitely say open a proposal.

It should be fairly straightforward - take the existing init property proposal and modify as necessary for fields.

[msedi]

@YairHalberstadt: Thanks for verifying this. I will try to open a proposal with some example for this.

[PathogenDavid]

If you do make a proposal, you should point out that this would allow taking the address of the field in unsafe scenarios.

You can convince the JIT to inline enough to take a pointer to the backing field, but it isn't pretty:

TakesIntPtr((int*)Unsafe.AsPointer(ref Unsafe.AsRef(point.Y)));

It also doesn't always work. (M2_Ref is copying the struct onto the stack in both the TakesInt and TakesIntPtr cases.)