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.

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

Jump to bottom

What is HEAD? #49

Closed
AlexDaniel opened this issue Oct 15, 2016 · 2 comments
Closed

What is HEAD? #49

AlexDaniel opened this issue Oct 15, 2016 · 2 comments
Labels
committable Issues related to Committable bot good first issue Low-hanging fruit (relatively easy issue, good for drive-by contributions)

Comments

@AlexDaniel
Copy link
Member 

10:56:12 <bartolin> committable6: 2016.09,HEAD say (my int $ = 2**32) * (my int $ = 2**63)
10:56:13 <committable6> bartolin, ¦«2016.09»: 0␤¦«HEAD»: This type cannot unbox to a native integer: P6opaque, Failure␤  in block <unit> at /tmp/5gdU3BwADu line 1␤ «exit code = 1»

It says ¦«HEAD» but gives no information on how old it actually is. Should we print something like ¦«HEAD(ffeeaa22)» ?
@AlexDaniel AlexDaniel added committable Issues related to Committable bot good first issue Low-hanging fruit (relatively easy issue, good for drive-by contributions) labels Oct 15, 2016
@AlexDaniel AlexDaniel added the testneeded Issue is generally resolved but tests were not written yet label Jan 6, 2017
@AlexDaniel
Copy link
Member Author

@MasterDuke17 what do you think?

AlexDaniel added a commit that referenced this issue Mar 4, 2017
@AlexDaniel
Lots of refactoring and other code mangling
bbede98 
This commit introduces some functional changes and some minor code
style tweaks.

Issues resolved: #32 #34 #48 #49 #50 #67 #70 #88 #95 #102 #103 #105

Kids, do not try this at home. Try to work on each issue separately.

Funtions that were returnings lists of things are a leftover from the
old times. For now, these were changed to return hashes, but some time
later these may start returning an object of some class.

Subclassing a Str was an interesting idea to make filters
work. However, mixing in some roles is probably more appropriate (but
still a bit unusual).

｢help｣ method is now actually required because of a stub in Helpful
role.

*Many* other changes as well, but given that all this was done in one
go, it is hard to highlight everything that was changed.

I consider all code style changes not very important, but with a code
base that is using two styles randomly, I'd much rather like
everything to be consistent. Therefore, here is an incomplete list:
* Avoid parens when possible, unless parens add clarity
* Prefer no semicolon if not needed
* Prefer trailing commas
* Prefer no “return” (unless it adds clarity)
* Prefer unicode ops and quotes
* Try to fit into some reasonable line length (80, or at least 120)
* Prefer $msg over $message (it is too common in this project)
* Prefer ｢with｣ and ｢without｣ instead of ｢if defined｣
* Lines with ｢use …;｣ are sorted alphabetically
@AlexDaniel
Copy link
Member Author

Fixed in bbede98

@AlexDaniel AlexDaniel removed the testneeded Issue is generally resolved but tests were not written yet label Mar 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
committable Issues related to Committable bot good first issue Low-hanging fruit (relatively easy issue, good for drive-by contributions)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AlexDaniel