Rename e{objc,swift} to {objc,swift}e #141
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thoughts @ultramiraculous @tomaskraina? |
|
Yeah...I had a coworker grumble about this the other day. My complaint here would be that I've personally gotten used to Nobody wants to double down on this and just define |
hmm, I guess that's possible too… |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #121, two new chisel commands were added
eobjcandeswift, for explicitly evaluating with a specific language. However this impacts the sanctity of theecommand in lldb 😜. Sure I can from now on useexwhere I previously usede, but we could also change the convention of how these commands are named.