Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: mention struct update syntax #37

Merged
merged 6 commits into from
Mar 19, 2024
Merged

Conversation

fitzchivalrik
Copy link
Contributor

When talking about the with expression in C#,
mention the struct update syntax1 as something
similar in Rust.

Footnotes

  1. https://doc.rust-lang.org/stable/book/ch05-01-defining-structs.html#creating-instances-from-other-instances-with-struct-update-syntax

When talking about the `with` expression in C#,
mention the struct update syntax [1] as something
similar in Rust.

[1]: https://doc.rust-lang.org/stable/book/ch05-01-defining-structs.html#creating-instances-from-other-instances-with-struct-update-syntax
Copy link
Contributor

@atifaziz atifaziz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. The struct update syntax is something certainly worth mentioning, but I don't think it's comparable to with. For example, if Point is part of some module then the fields x and y would be private to the code that's external to the module. The Point would then have to be defined as:

mod points {
    #[derive(Debug)]
    pub struct Point { pub x: i32, pub y: i32 }
}

fn main() {
    use points::Point;
    let pt = Point { x: 123, y: 456 };
    let pt = Point { x: 789, ..pt };
    println!("{pt:?}"); // prints: Point { x: 789, y: 456 }
}

to use the struct update syntax from outside the module. Also note that if you make the fields public then the whole impl block can be skipped. Consequently, the emulation example is still valid so I would leave it intact but then add your bits about the struct update syntax with the above example. I would then point out that it's generally more common to see that use within the module that has access to private details of its types.

@fitzchivalrik
Copy link
Contributor Author

fitzchivalrik commented Apr 8, 2023

For example, if Point is part of some module then the fields x and y would be private to the code that's external to the module.

Yeah, I was debating whether that should be mentioned explicitly, or if it would complicate things too much.
I decided to not mention it, because I thought it is the same for with; as in, the fields need to be accessible at call site to be able to use with:

using System;

public readonly record struct Point {
	internal readonly int X {get; init;}
	private readonly int Y {get; init;}
	public Point(int x, int y) => (X,Y)=(x,y);
	public override String ToString() => $"Point {{ X = {this.X}, Y= {this.Y} }}";
}
public class Program
{
	public static void Main()
	{
		var pt = new Point(123, 456);
		pt = pt with { X = 789 }; // Error if `X` is declared private above, or if `Main()` is in another project/module.
		Console.WriteLine(pt.ToString()); // prints: Point { X = 789, Y = 456 }
	}
}

@atifaziz
Copy link
Contributor

atifaziz commented Apr 8, 2023

I thought it is the same for with; as in, the fields need to be accessible at call site to be able to use with

Right, but in the C# example, X and Y are properties, not fields, and so it's comparing apples to oranges.

Add struct update syntax as additional information,
do not remove mention of explicit constructs to emulate a
`with`. 
Also mention that fields need to be accessible to use the syntax.
@fitzchivalrik
Copy link
Contributor Author

but in the C# example, X and Y are properties, not fields,

Ah, yeah, fair point! Thank you!

Copy link
Contributor

@atifaziz atifaziz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've made a few suggestions then we're good to merge. 🏁

src/language/custom-types/members.md Outdated Show resolved Hide resolved
src/language/custom-types/members.md Outdated Show resolved Hide resolved
Copy link
Contributor

@atifaziz atifaziz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just had a thought. Perhaps it's best to compare the struct update syntax of Rust with non-destructive mutation of non-record struct types using with, which has been possible since C# 10. It seems a lot more comparable. The difference is that C# does a non-destructive mutation (copy then update) whereas Rust does (partial) moves. I would suggest starting with a C# example of Point as a struct with public and (read-write) fields:

var pt = new Point { X = 123, Y = 456 };
Console.WriteLine(pt.ToString()); // prints: (123, 456)
pt = pt with { X = 789 };
Console.WriteLine(pt.ToString()); // prints: (789, 456)

struct Point
{
    public int X;
    public int Y;

    public override string ToString() => $"({X}, {Y})";
}

Then go on to show the same is possible in Rust using the struct update syntax and end on the differences.

Instead of record structs, as a plain struct is more comparable to Rust's.
@fitzchivalrik
Copy link
Contributor Author

I updated it according to the suggestions - at least, I hope I understood them correctly ^^.
I am not sure, however, if the last bit with the 'bake into type' still makes sense there, or if it maybe should be changed to a 'copy'-style update, instead of a consuming one.

@atifaziz atifaziz mentioned this pull request Apr 13, 2023
16 tasks
Copy link
Contributor

@atifaziz atifaziz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry this took so long, @fitzchivalrik, but I integrated the final edits with d655d1b and this is good to go now!

Thanks for contribution and working through the review!

@atifaziz
Copy link
Contributor

@fitzchivalrik If you could agree to the CLA then I can get this merged. Thanks!

@fitzchivalrik
Copy link
Contributor Author

@atifaziz No worries, thanks for coming back to it.
Unfortunately, I do not really want to agree to the CLA.
(I am unsure if this contribution even passes the threshold of originality, but I am not a lawyer, of course.)

If this causes complications, I would be open to agree to the CLA only for this specific contribution (and not in general), if this is at all possible.

@atifaziz
Copy link
Contributor

If this causes complications, I would be open to agree to the CLA only for this specific contribution (and not in general), if this is at all possible.

@fitzchivalrik I understand. How about this? You sign it now for this contribution and if you feel uncomfortable with the CLA at any point thereafter and want to revoke it for future contributions, you always have the option to terminate the agreement by issuing the following command:

@microsoft-github-policy-service terminate

However, I'd encourage you to seek clarity on the CLA so you're eventually comfortable with it because we appreciate and value your contributions!

@fitzchivalrik
Copy link
Contributor Author

Sorry for the delay. Thanks for the terminate command - agreeing, and then terminating it later here is fine for me.
@microsoft-github-policy-service agree

@atifaziz atifaziz merged commit 438cf30 into microsoft:main Mar 19, 2024
3 checks passed
@fitzchivalrik
Copy link
Contributor Author

@microsoft-github-policy-service terminate

Copy link
Contributor

@fitzchivalrik please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

  1. Definitions.
    “Code” means the computer software code, whether in human-readable or machine-executable form,
    that is delivered by You to Microsoft under this Agreement.
    “Project” means any of the projects owned or managed by Microsoft and offered under a license
    approved by the Open Source Initiative (www.opensource.org).
    “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
    Project, including but not limited to communication on electronic mailing lists, source code control
    systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
    discussing and improving that Project, but excluding communication that is conspicuously marked or
    otherwise designated in writing by You as “Not a Submission.”
    “Submission” means the Code and any other copyrightable material Submitted by You, including any
    associated comments and documentation.
  2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
    Project. This Agreement covers any and all Submissions that You, now or in the future (except as
    described in Section 4 below), Submit to any Project.
  3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
    Should You wish to Submit materials that are not Your original work, You may Submit them separately
    to the Project if You (a) retain all copyright and license information that was in the materials as You
    received them, (b) in the description accompanying Your Submission, include the phrase “Submission
    containing materials of a third party:” followed by the names of the third party and any licenses or other
    restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
    guidelines concerning Submissions.
  4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
    for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
    Submission is made in the course of Your work for an employer or Your employer has intellectual
    property rights in Your Submission by contract or applicable law, You must secure permission from Your
    employer to make the Submission before signing this Agreement. In that case, the term “You” in this
    Agreement will refer to You and the employer collectively. If You change employers in the future and
    desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
    and secure permission from the new employer before Submitting those Submissions.
  5. Licenses.
  • Copyright License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
    Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
    the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
    parties.
  • Patent License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
    Your patent claims that are necessarily infringed by the Submission or the combination of the
    Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
    import or otherwise dispose of the Submission alone or with the Project.
  • Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
    No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
    granted by implication, exhaustion, estoppel or otherwise.
  1. Representations and Warranties. You represent that You are legally entitled to grant the above
    licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
    have disclosed under Section 3). You represent that You have secured permission from Your employer to
    make the Submission in cases where Your Submission is made in the course of Your work for Your
    employer or Your employer has intellectual property rights in Your Submission by contract or applicable
    law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
    have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
    You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
    REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
    EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
    PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
    NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
  2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
    You later become aware that would make Your representations in this Agreement inaccurate in any
    respect.
  3. Information about Submissions. You agree that contributions to Projects and information about
    contributions may be maintained indefinitely and disclosed publicly, including Your name and other
    information that You submit with Your Submission.
  4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
    the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
    Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
    exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
    defenses of lack of personal jurisdiction and forum non-conveniens.
  5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

@fitzchivalrik fitzchivalrik deleted the patch-3 branch June 12, 2024 21:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants