<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/src/test/ui/parser/expr-as-stmt.rs, branch 1.41.0</title>
<subtitle>https://github.com/rust-lang/rust
</subtitle>
<id>http://git.dreamy.place/mirrors/rust/atom?h=1.41.0</id>
<link rel='self' href='http://git.dreamy.place/mirrors/rust/atom?h=1.41.0'/>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/'/>
<updated>2019-05-01T03:37:42+00:00</updated>
<entry>
<title>Reword ambigous parse error to fit with the current error</title>
<updated>2019-05-01T03:37:42+00:00</updated>
<author>
<name>Esteban Küber</name>
<email>esteban@kuber.com.ar</email>
</author>
<published>2019-05-01T03:37:42+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=617ce2b7ee330bbcc7ce8eb87160c71ad995639b'/>
<id>urn:sha1:617ce2b7ee330bbcc7ce8eb87160c71ad995639b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add test case for #47287</title>
<updated>2019-04-29T21:35:09+00:00</updated>
<author>
<name>Esteban Küber</name>
<email>esteban@kuber.com.ar</email>
</author>
<published>2019-04-29T21:35:09+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=bff0be37845a96010fa2161bbf137fadfe763ae5'/>
<id>urn:sha1:bff0be37845a96010fa2161bbf137fadfe763ae5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Identify when a stmt could have been parsed as an expr</title>
<updated>2019-04-29T21:07:02+00:00</updated>
<author>
<name>Esteban Küber</name>
<email>esteban@kuber.com.ar</email>
</author>
<published>2019-04-23T02:37:23+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=f007e6f442adafae3e5f2f7f635dc12463bbe0bb'/>
<id>urn:sha1:f007e6f442adafae3e5f2f7f635dc12463bbe0bb</id>
<content type='text'>
There are some expressions that can be parsed as a statement without
a trailing semicolon depending on the context, which can lead to
confusing errors due to the same looking code being accepted in some
places and not others. Identify these cases and suggest enclosing in
parenthesis making the parse non-ambiguous without changing the
accepted grammar.
</content>
</entry>
</feed>
