-
Notifications
You must be signed in to change notification settings - Fork 75
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
Feature Request: Line-level Inline Exclusions #91
Comments
Hi @ChefAustin! Thanks for the suggestion, I see it is well accepted by looking at the number of upvotes. Do you potentially have the bandwidth to try to do a proof of concept how it would work? |
I very much wish I currently had the free time to do a PoC on this feature. I am hoping that in the coming months I might be able to get around to poking at it. When I do eventually have the time, I'll need to first do a deep-dive into the mechanics of |
Sounds good! :) If there isn't any movement on this in the next 6 months, i'll close it out :) |
Any chance of merging the open PR that adds this functionality? Currently |
Would love this too 😿 |
I think it would be a great enhancement if I was able to disable/exclude a speed suggestion for a specific line via a magic comment (much like how Rubocop does single-instance cop-disablement;
# rubocop:disable Metrics/LineLength
).There are times where a single
speedup
in a given line of code is not applicable and I want to disable thespeedup
for the line but I don't want to have to add the entire file to theexclude_paths
block of.fasterer.yml
.For example, if I have instance whereby I've used
Hash#keys.each
two times in a single file and one of those two times the hash is modified during the.each
block (but the other time, the hash is not modified during the.each
block) then I would wantfasterer
to ignore that singular instance ofHash#keys.each
where the hash is modified (while still lettingfasterer
analyze the other instance ofHash#keys.each
where the hash is not modified).Hopefully this makes sense and seems reasonable!
Thanks for all the work put into
fasterer
over the years; it has certainly made some of my code... well...fasterer
. 😄The text was updated successfully, but these errors were encountered: