Talk:Rust (programming language)

Add WebAssembly as a target?

Should we add WASM as a listed target? I'm leaning towards no since it's only a "guaranteed to build" target and not a "guaranteed to work" target. 199.58.98.69 (talk) 03:47, 31 July 2019 (UTC)

I'm surprised that WebAssembly isn't included in the list of platforms in this article. Is WebAssembly not a "platform?" Jarble (talk) 16:11, 15 January 2021 (UTC)

The fact that, in your words, it is a "guaranteed to build" target makes me all for inclusion Scaledish! Talkish? Statish. 15:16, 25 May 2021 (UTC)

Please add a section about side effects in Rust

Please add a section about side effects in Rust. --VictorPorton (talk) 04:16, 7 August 2020 (UTC)

Such as? War (talk) 07:07, 7 August 2020 (UTC)

I believe he confused this article with the article on rust (on metal) Scaledish! Talkish? Statish. 01:43, 16 May 2021 (UTC)

Mozilla layoffs and a Rust foundation

Since when are twitter tweets reliable sources for wiki pedia?

Even from people involved in a matter, i.e. non-neutral sources?

Jan Burse (talk) 15:34, 29 January 2021 (UTC)

Variables assigned multiple times must be marked with the keyword mut

Isn't a mutable variable a tautology?

What is wrong with const x: int = 1; and let x: int = 1;? OttTheTormentor (talk) 21:21, 8 February 2021 (UTC)

No, mutable variable is not a tautology, it is an established word combination in computer science. Another established word combination which looks like a tautology is constant variable.

In Rust, every variable is constant by default (can be made mutable with mut). This is just how the language was defined. Anton.bersh (talk) 11:26, 18 April 2021 (UTC)

Misleading/False advertising of Rust's support for IA32 (32 bit) Platforms

The Rust programming language support for IA32 (32 bit) platoforms is almost completely misleading or false advertising.

Rust removed support for CPU's not having SSE2 optimization register within the past year, or was in the process of removing two or more years ago.

The CPU SSE2 optimization register was only fully implented on very late era Intel Pentium 4 CPU's. (See Wikipedia SSE2 article.) Prior to Pentium 4, the SSE2 register was called the MMX CPU register, and to use the MMX register as a SSE2 register would require additional trivial coding. MMX register, again, was only implemented in late era Pentium CPU's.

In brief, Rust programming language seems to have been quietly removing support for the older non-SSE2 CPU's over the past year, quietly subsequently creating havoc within coding and Linux package maintainer social environments, as Rust now only provides SSE2 bootstrap builds. All awhile still advertising IA32 support. A platform not having the SSE2 CPU register executing SSE2 compiled code will usually immediately segfault, and if any error message is given, a very generic error message until digging deeper. --roger (talk) 19:14, 22 February 2021 (UTC)

Rust is not a commercial product therefore it can't exhibit "false advertising." Also, are there 'any' IA32 processors manufactured in the last 15 years that don't support SSE2? War (talk) 06:39, 26 February 2021 (UTC)

Also, until recently Rust could not build 32 bit because of bug in LLVM. That has been fixed. see: https://github.com/rust-lang/rust/pull/81451 War (talk) 00:10, 9 March 2021 (UTC)

Inclusion of rust components as a part of the rust feature set

The following discussion is an archived record of a request for comment. Please do not modify it. No further edits should be made to this discussion.

A summary of the debate may be found at the bottom of the discussion.

---

A strong part of rust are the components. we have cargo, clippy, rustfmt, rust-docs and more. I would like to raise the question of if these components should be included in the rust wikipedia page

For

• Many of these components are included in the rust source tree (not all)
• A valid thing rust has going for it *is* this ecosystem, It is silly to ignore
• I would argue cargo especially is a part of the core of rust - even if not needed.

Against

• Components are managed by rustup. rustup is developed by rust, but is not "core" (ie a secondary project)
• Technically, the rust lang is just the rustc component - nothing more is needed (ie the lang breaks without it) (although all the components help a lot!)
• Not all components are developed in the core rust source tree

Solutions

• Separate article for rust components
• Inclusion under the features section
• New category.

Discussion

What are your thoughts on this? Scaledish! Talkish? Statish. 01:40, 16 May 2021 (UTC)

Aren't module dependencies handled by cargo? If so, that seems like a compelling reason for including it. I weakly support including the entire ecosystem. Shmuel (Seymour J.) Metz Username:Chatul (talk) 03:48, 16 May 2021 (UTC)

This was what raised the question in the first place for me. I was alarmed to not discover any reference to cargo, and while researching with the intent to include it, I remembered all the other tools. Perhaps the best course of action would first be a study on how other dependency managers are handled in other articles. Upon a brief glance, here is what I discovered

• Python (programming language)'s only reference to the package manager is a link to Pip (package manager)
• Node.js has many references to Npm (software), although Npm has its own article

Next, I looked at Java (programming language) and PHP but I could not find any official connection

I was thinking it was looking bad for the inclusion in this article, and that a new article was needed. Then I thought... Go (programming language), Go and rust are both modern langs, and alas we find Go (programming language)#Tools, very similar to rust components. In my mind, this is a triumph, however I am interested to see other's inputs Scaledish! Talkish? Statish. 15:47, 16 May 2021 (UTC)

Suggest including (invited by the bot) I don't have expertise here but if they are components of crust it's hard to imaging a reason to not include them. Can be brief if that is appropriate. North8000 (talk) 17:30, 16 May 2021 (UTC)

Conclusion: I think it is clear based on Go (programming language) what to do, however if someone has any objections to the inclusion I will hear them out and we can discus moving the new section. Until then, This RFC is closed. Thanks everyone for the input! Scaledish! Talkish? Statish. 18:58, 17 May 2021 (UTC)

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.

@Scaledish: Please keep the section to a reasonable length. The entire components set or the Cargo file structure is too much. —Dexxor (talk) 04:56, 18 May 2021 (UTC)

I tried to remove the irrelevant components and will continue doing so as I write. Why do you consider the Cargo section too much, especially considering it is under a minimized by default drop-down? Thanks, Scaledish! Talkish? Statish. 13:09, 18 May 2021 (UTC)

Additionally, I would like to invite @Dexxor: and anyone else to suggest components to include/exclude from the article (Please see the todo list first!). (Unsure if the reply feature mentions, if not see above comment, thanks) Scaledish! Talkish? Statish. 13:33, 18 May 2021 (UTC)

 Done Scaledish! Talkish? Statish. 12:54, 9 June 2021 (UTC)

Rust is high-level

If the user who says Rust is not high-level wants to create an account and discuss here (or if anyone else wants to voice an opinion), please do. Caleb Stanford (talk) 01:58, 12 November 2021 (UTC)

Add a Controversy sub-section to Governance?

The rust moderation team seems to have publicly resigned en-masse. This is being further discussed on Reddit here, and is purportedly due to a lack of 'Core Team' oversight. This seems to be a sufficiently big deal to merit a mention, but of course hasn't been resolved yet.