From: Nicholas Bishop Date: Sat, 2 May 2015 23:15:00 +0000 (-0400) Subject: Fix a missing word in the README X-Git-Url: https://git.lizzy.rs/?a=commitdiff_plain;ds=sidebyside;h=1ef94acec11b6f33795455ca47f43f8e62652259;p=rust.git Fix a missing word in the README --- diff --git a/README.md b/README.md index 74ed52129a4..54a8bfc4c2f 100644 --- a/README.md +++ b/README.md @@ -88,7 +88,7 @@ when making those changes. The advantage of the tokens approach are that you can operate on non-parsable code. I don't care too much about that, it would be nice, but I think being able -to sophisticated transformations is more important. In the future I hope to +to perform sophisticated transformations is more important. In the future I hope to (optionally) be able to use type information for informing reformatting too. One specific case of unparsable code is macros. Using tokens is certainly easier here, but I believe it is perfectly solvable with the AST approach. At the limit,