Skip to content

Fix typo/missing lines in comment in test #40

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 16, 2015
Merged

Fix typo/missing lines in comment in test #40

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion rust-mode-tests.el
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1124,12 +1124,14 @@ supposed to back out of all parens, but `beginning-of-defun'
could leave it inside parens if a fn appears inside them.

Having said that, as I write this I don't understand fully what
internal state was corruped and how. There wasn't an obvious
internal state was corrupted and how. There wasn't an obvious
pattern to what did and did not trip it."

;; When bug #36 was present, the following test would pass, but running it
;; caused some unknown emacs state to be corrupted such that the following
;; test failed. Both the "blank_line" and "indented_closing_brace" functions
;; were needed to expose the error, for instance--deleting either of them
;; would make the failure go away.
(with-temp-buffer
(rust-mode)
(insert "fn blank_line(arg:int) -> bool {
Expand Down