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

Checklist for 2019.03 #2673

Closed
11 tasks done
JJ opened this issue Mar 14, 2019 · 7 comments · Fixed by #2818
Closed
11 tasks done

Checklist for 2019.03 #2673

JJ opened this issue Mar 14, 2019 · 7 comments · Fixed by #2818
Labels
big Issue consisting of many subissues checklist Items added in a recent Rakudo release docs Documentation issue (primary issue type) help wanted We need some help here versions Version issues: old behavior still described, things that need a explicit version number...

Comments

@JJ
Copy link
Contributor

JJ commented Mar 14, 2019

Check the announcement here

Additions:

Removals:

  • Removed ComptUnit::Repository::Installation and Distribution
    compatibility shims for old versions of panda and zef -f430518f
  • Renamed Block/WhateverCode.pos to .POSITIONS -ccf350e4
@JJ JJ added docs Documentation issue (primary issue type) big Issue consisting of many subissues help wanted We need some help here labels Mar 15, 2019
@JJ JJ added the versions Version issues: old behavior still described, things that need a explicit version number... label Mar 25, 2019
@taboege taboege self-assigned this May 19, 2019
taboege added a commit to taboege/doc that referenced this issue May 20, 2019
X::Control got the ability to turn exceptions into control exceptions
in 2019.03. Part of Raku#2673 and also refs Raku#2551.
@taboege
Copy link
Member

taboege commented May 20, 2019

Please see #2818.

Points 1, 3, 5, 7 and the removals didn't require any action. They were documented parallel to the additions (lizmat++, ugexe++) or, in case of removals, weren't documented anyway.

The current PR doesn't address the is Type[Parameters] trait point because I feel like that this is more of a bugfix. Reading the documentation as it is now, I would expect is to work with parameterized types just like with any other.

I did not include a mention of @jnthn's explanation of shortcomings of the current X::Control control exception throwing. Should I?

@JJ JJ closed this as completed in #2818 May 20, 2019
@JJ
Copy link
Contributor Author

JJ commented May 20, 2019

If they are spec, why not...

@JJ
Copy link
Contributor Author

JJ commented Jun 16, 2019

I'm going to reopen for several reasons:

  • The parametrized trait would need an example. It's maybe a bugfix, but still.
  • Also that issue raises another number of issues, including the documentation of "parameterized" in ParametricRoleHOW and ParametricRoleGroupHOW.
  • Also, Document "method ^foo" syntax #2856

@codesections codesections added the checklist Items added in a recent Rakudo release label Aug 29, 2020
@coke
Copy link
Collaborator

coke commented Aug 30, 2020

Checked the last item

Allowed is Type trait to handle parameterization like
is Set-Int -2ed2f398

Which is already covered in doc/Type/Set.pod6

@coke coke closed this as completed Aug 30, 2020
@coke
Copy link
Collaborator

coke commented Aug 30, 2020

Re-opening, as @JJ's comment from Jun indicates more work needed to be done that isn't covered by the checklist status.

@coke coke reopened this Aug 30, 2020
JJ added a commit that referenced this issue Aug 21, 2021
JJ added a commit that referenced this issue Aug 21, 2021
And adding one for `Array` as requested by #2673
@JJ
Copy link
Contributor Author

JJ commented Aug 21, 2021

Took me a while to understand that Type does not really refer to an actual class called that way, but to a generic type. Sometimes, you need to act fast to request additional information, or you'll be left a bit confused by what's written.

JJ added a commit to JJ/my-raku-examples that referenced this issue Aug 22, 2021
JJ added a commit to JJ/my-raku-examples that referenced this issue Aug 22, 2021
JJ added a commit that referenced this issue Aug 22, 2021
@coke
Copy link
Collaborator

coke commented Mar 5, 2023

Re-opening, as @JJ's comment from Jun indicates more work needed to be done that isn't covered by the checklist status.

JJ himself committed the example he was looking for, and #3353 covers the other issue.

Everything else checked, closing.

@coke coke closed this as completed Mar 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
big Issue consisting of many subissues checklist Items added in a recent Rakudo release docs Documentation issue (primary issue type) help wanted We need some help here versions Version issues: old behavior still described, things that need a explicit version number...
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants