Skip to content

Fix in-line forall highlighting #170

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.

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

Conversation

ChrisspyB
Copy link
Contributor

This is intended to fix issue #169, which reported that single-line forall statements have have incorrect highlighting. The error arrises because the existing patterns assume that all forall statements end with an end forall. However, this is not true of single-line statements.

This solution follows the already implemented patterns of the where statement, which has a very similar syntax.

Before Change

Screenshot 2020-04-11 at 06 14 47

After change

Screenshot 2020-04-11 at 06 13 50

Side note: an identical issue and resolution can be found in a Fortran highligter made for Atom (dparkins/language-fortran#90).

@pedro-ricardo pedro-ricardo mentioned this pull request Apr 11, 2020
13 tasks
@pedro-ricardo pedro-ricardo changed the base branch from master to release/2.2.0 April 11, 2020 12:29
@pedro-ricardo pedro-ricardo merged commit e817c59 into fortran-lang:release/2.2.0 Apr 11, 2020
pedro-ricardo added a commit that referenced this pull request May 15, 2020
### Check List
- Highlight
- [x] `select` keyword - *Merge #165 to fix #149*
- [x] `rank` keyword -  *Merge #165*
- [x] `forall` keyword - *Merge #170 to fix #169*
- Symbol List
- [x] Symbols bug in VSCode +1.40 - *Merge #161 to fix #154*
- [x] Symbols classification - *Merge #141 to fix #140*
- [x] Long named symbols - *Merge #151*
- Settings
- [x] Add more options - *Merge #152*
- Dependencies
- [x] Merge `dependabot` PR's
    - [x] lodash - *Merge #144*
    - [x] mixin-deep - *Merge #146*
    - [x] handlebars - *Merge #155* 
- Code Completion
- [x] Array constructor - *Fix #148*
- New Features
- [x] Breakpoints - *Merge #150*
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants