Talk:Typestate analysis
Add topicLatest comment: 2 months ago by Rudxain in topic "Typestate" employed in Rust's move semantics
| This is the talk page for discussing improvements to the Typestate analysis article. This is not a forum for general discussion of the subject of the article. |
Article policies
|
| Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
 | This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||
Static vs. dynamic analysis
[edit]- The article should mention explicitly whether typestate analyses are performed during runtime ("dynamically") or before ("statically"). Possibly, this may differ depending on the supporting tools/languages.
- Abstract interpretation-based analysis seems to be useful to detect possible aliases. If this technique is in fact employed by some approach, an appropriate cross-link could be given in the article.
"Typestate" employed in Rust's move semantics
[edit]This text says: "Other examples include the Clara[18] language research framework, earlier versions of the Rust language, and the >> keyword in ATS.[19]". But as far as I know, one of Rust's core innovations is that it tracks if a variable has been moved out, so later code cannot read from a variable anymore. 79.218.67.102 (talk) 06:36, 11 June 2018 (UTC)
- I agree. Rust has built-in support for a subset of generalized type-state. But for general purpose use, it has to be done manually[1] Rudxain (talk) 16:09, 24 May 2026 (UTC)
- ↑ L. Biffle, Cliff (2019-06-05). "The Typestate Pattern in Rust". Retrieved 2026-05-24.