Skip to content
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

Remove Redundant Goto Statements #615

Closed
wants to merge 2 commits into from

Conversation

ShounakDas101
Copy link
Contributor

Solves issue #526. We can only remove the goto stmt only when return statement is not inside any control flow statement

Solves issue vgvassilev#526. We can only remove the goto stmt only when return statement is not inside any control flow statement
@github-actions
Copy link
Contributor

clang-tidy review says "All clean, LGTM! 👍"

@codecov
Copy link

codecov bot commented Aug 10, 2023

Codecov Report

Merging #615 (16c4b59) into master (790d978) will decrease coverage by 0.08%.
The diff coverage is 100.00%.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #615      +/-   ##
==========================================
- Coverage   93.83%   93.76%   -0.08%     
==========================================
  Files          41       41              
  Lines        6032     6042      +10     
==========================================
+ Hits         5660     5665       +5     
- Misses        372      377       +5     
Files Changed Coverage Δ
include/clad/Differentiator/ReverseModeVisitor.h 98.70% <ø> (ø)
lib/Differentiator/ReverseModeVisitor.cpp 95.62% <100.00%> (+0.02%) ⬆️

... and 1 file with indirect coverage changes

Files Changed Coverage Δ
include/clad/Differentiator/ReverseModeVisitor.h 98.70% <ø> (ø)
lib/Differentiator/ReverseModeVisitor.cpp 95.62% <100.00%> (+0.02%) ⬆️

... and 1 file with indirect coverage changes

@github-actions
Copy link
Contributor

clang-tidy review says "All clean, LGTM! 👍"

@vgvassilev
Copy link
Owner

Please stop opening new pull requests. I strongly encourage you to work on #608

in addition as part of our meeting we have proposed an entry point tasks to get to know the code base and git. We strongly encourage you to do that rather than keeping bombarding the repository with such PRs.

@vgvassilev vgvassilev closed this Aug 10, 2023
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