Jump to content

Talk:Rust (programming language)/GA1

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 0xDeadbeef (talk | contribs) at 10:27, 14 July 2022 (done a few). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

GA Review

GA toolbox
Reviewing

Article (edit | visual edit | history) · Article talk (edit | history) · Watch

Reviewer: Hawkeye7 (talk · contribs) 03:53, 14 July 2022 (UTC)[reply]

Picking this one up. Review to follow. Hawkeye7 (discuss) 03:53, 14 July 2022 (UTC)[reply]

Comments

Article looks in reasonable shape. Some work required.

  • Lead
    • Last paragraph of the lead is not covered in the body. I would move all but the first sentence into the body.
       Done. 0xDeadbeef
  • Evolution (2013–2019)
    • "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.
       Done by rewording it to type system. 0xDeadbeef
    • Combine the first two and last two paragraphs.
       Done. 0xDeadbeef
    • Link C++
       Done. 0xDeadbeef
  • Mozilla Layoffs and Rust Foundation (2020–present)
    • Combine the first two and last two paragraphs.
       Done. 0xDeadbeef
    • The last two also need combining or folding in, but also require a bridge to avoid to sentences running starting with "On <date>..."
       Done. 0xDeadbeef
  • Hello, World program
    • Should we mention that the bang indicates a macro instead of a function?
       Done. 0xDeadbeef
  • Syntax and semantics
    • Entire section is unreferenced. References are required here.
  • Keywords and control flow
    • Might as well mention comments here as well, since you're using them
       Done. 0xDeadbeef
  • Expression blocks
    • "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?
       Done. 0xDeadbeef
  • Memory management
    • Citation required.
  • Ownership
    • Citation required.
  • Types and polymorphism
    • Citation required.
  • Cargo
    • Citation required.
  • IDE support
    • Citation required.
  • Performance
    • Merge sentences into one paragraph.
  • Adoption
    • Citation required.
  • Components
    • Can we describe the standard library?
  • Web browsers and services
    • Citation required.
  • Rust Foundation
    • Citation required.
  • Notes
    • Still require references.
  • References
    • fn 1, 104 - need access date
       Done. 0xDeadbeef
    • fn 1, 6, 7, 8, 12, 24, 38, 40, 42, 66, 69, 75, 85, 95, 96, 102, - need publisher
    • fn 34 - needs degree + university
       Done. 0xDeadbeef

GA review – see WP:WIAGA for criteria

  1. Is it well written?
    A. The prose is clear and concise, and the spelling and grammar are correct:
    B. It complies with the manual of style guidelines for lead sections, layout, words to watch, fiction, and list incorporation:
  2. Is it verifiable with no original research?
    A. It contains a list of all references (sources of information), presented in accordance with the layout style guideline:
    B. All in-line citations are from reliable sources, including those for direct quotations, statistics, published opinion, counter-intuitive or controversial statements that are challenged or likely to be challenged, and contentious material relating to living persons—science-based articles should follow the scientific citation guidelines:
    C. It contains no original research:
    D. It contains no copyright violations nor plagiarism:
  3. Is it broad in its coverage?
    A. It addresses the main aspects of the topic:
    B. It stays focused on the topic without going into unnecessary detail (see summary style):
  4. Is it neutral?
    It represents viewpoints fairly and without editorial bias, giving due weight to each:
  5. Is it stable?
    It does not change significantly from day to day because of an ongoing edit war or content dispute:
  6. Is it illustrated, if possible, by images?
    A. Images are tagged with their copyright status, and valid non-free use rationales are provided for non-free content:
    B. Images are relevant to the topic, and have suitable captions:
  7. Overall:
    Pass or Fail:
    Quite good. Putting on hold pending changes.
    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? 0xDeadbeef 06:43, 14 July 2022 (UTC)[reply]
  1. WP:ABOUTSELF only applies to biographies. Citing a book about the Rust programming language is precisely what is required. Hawkeye7 (discuss) 08:07, 14 July 2022 (UTC)[reply]