The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
"Rust's object system, used for object-oriented programming" Hang on. You said in the lead that it was a functional language, not an object oriented one.
"if the semicolon is omitted, the last expression in the function will be used as the return value" The last expression, or the value of the last expression?
McNamara, Tim (2021). Rust in Action (1st ed.). Manning Publications.
ISBN9781617294556. (already cited once in the article) says:
"Sadly, though, Rust has a fairly tight standard library. As with regular expressions, another area with relatively minimalist support is handling command-line arguments." (p. 71)
"Rust's standard library is comparatively slim. It excludes numeric types that are often available within other languages. These include: Many mathematical objects for working with rational numbers and complex numbers; arbitrary-size integers and arbitrary-precision floating-point numbers ... fixed-point decimal numbers for working with currencies" (p.43)
"Rust's standard library tends to lack many things that other languages provide, like random number generators and regular expression support. That means it's common to incorporate third-party crates into your project." (p.67)
I think it's alright to cite a primary source as well, i.e.
[1]. And maybe it's worth noting that you can exclude std if desired.
Ovinus (
talk)
18:50, 14 July 2022 (UTC)reply
Usually for things like programming languages and technology, primary sources are OK. Theres a guideline somewhere, I forget where it is, but I know the conesnsus is that its less strict then living people and historical events.
Rlink2 (
talk)
21:34, 14 July 2022 (UTC)reply
Thank you,
User:Hawkeye7, I suppose the use of
WP:ABOUTSELF sources in the technical sections would not prevent it from passing the GA? Or is there a need to reference the book "The Rust Programming Language (Covers Rust 2018)" in addition? 0x
Deadbeef06:43, 14 July 2022 (UTC)reply
All good for GA. Great work. I made some (very) minor changes to resolve a disambig, suppress a warning (which most people would never see), reformat an ISBN (cosmetic) and reference an unreferenced sentence. There are a quite a few duplicated links; I wasn't sure how you feel about these. If you take it to FAC, anticipate some probing questions about your sources. A couple of suggestions, largely from my curiosity:
The example in the macros section does not show you how one is written
The standard library stands out as a possible area for expansion. Footnote 1 implies that it is anything but.
Note 5 does not say anything. Suggest removing it or folding it into a footnote.
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
"Rust's object system, used for object-oriented programming" Hang on. You said in the lead that it was a functional language, not an object oriented one.
"if the semicolon is omitted, the last expression in the function will be used as the return value" The last expression, or the value of the last expression?
McNamara, Tim (2021). Rust in Action (1st ed.). Manning Publications.
ISBN9781617294556. (already cited once in the article) says:
"Sadly, though, Rust has a fairly tight standard library. As with regular expressions, another area with relatively minimalist support is handling command-line arguments." (p. 71)
"Rust's standard library is comparatively slim. It excludes numeric types that are often available within other languages. These include: Many mathematical objects for working with rational numbers and complex numbers; arbitrary-size integers and arbitrary-precision floating-point numbers ... fixed-point decimal numbers for working with currencies" (p.43)
"Rust's standard library tends to lack many things that other languages provide, like random number generators and regular expression support. That means it's common to incorporate third-party crates into your project." (p.67)
I think it's alright to cite a primary source as well, i.e.
[1]. And maybe it's worth noting that you can exclude std if desired.
Ovinus (
talk)
18:50, 14 July 2022 (UTC)reply
Usually for things like programming languages and technology, primary sources are OK. Theres a guideline somewhere, I forget where it is, but I know the conesnsus is that its less strict then living people and historical events.
Rlink2 (
talk)
21:34, 14 July 2022 (UTC)reply
Thank you,
User:Hawkeye7, I suppose the use of
WP:ABOUTSELF sources in the technical sections would not prevent it from passing the GA? Or is there a need to reference the book "The Rust Programming Language (Covers Rust 2018)" in addition? 0x
Deadbeef06:43, 14 July 2022 (UTC)reply
All good for GA. Great work. I made some (very) minor changes to resolve a disambig, suppress a warning (which most people would never see), reformat an ISBN (cosmetic) and reference an unreferenced sentence. There are a quite a few duplicated links; I wasn't sure how you feel about these. If you take it to FAC, anticipate some probing questions about your sources. A couple of suggestions, largely from my curiosity:
The example in the macros section does not show you how one is written
The standard library stands out as a possible area for expansion. Footnote 1 implies that it is anything but.
Note 5 does not say anything. Suggest removing it or folding it into a footnote.
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.