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
Implementation of 'infix:=>' for Rakudo #85
Comments
From @bacekHello. There is implementation of 'infix:=>' for Rakudo |
From @bacekp.diffIndex: src/parser/grammar-oper.pg
===================================================================
--- src/parser/grammar-oper.pg (revision 27566)
+++ src/parser/grammar-oper.pg (working copy)
@@ -128,6 +128,7 @@
proto infix:<:=> is equiv(infix:<=>) is pasttype('bind') { ... }
proto infix:<::=> is equiv(infix:<=>) { ... }
proto infix:<.=> is equiv(infix:<=>) { ... }
+proto infix:«=>» is equiv(infix:<=>) { ... }
proto infix:<~=> is equiv(infix:<=>) { ... }
proto infix:<+=> is equiv(infix:<=>) { ... }
proto infix:<-=> is equiv(infix:<=>) { ... }
Index: src/classes/Pair.pir
===================================================================
--- src/classes/Pair.pir (revision 27566)
+++ src/classes/Pair.pir (working copy)
@@ -137,7 +137,43 @@
.return($S2)
.end
+=item get_string() (vtable method)
+Return the pair in stringified form
+
+=cut
+
+.sub 'get_string' :vtable :method
+ $P0 = self.'perl'()
+ .return ($P0)
+.end
+
+=head1 Functions
+
+=cut
+
+.namespace
+
+=item infix:=>
+
+Create Pair
+
+=cut
+
+.sub 'infix:=>'
+ .param pmc key
+ .param pmc value
+ .local pmc pair
+
+ pair = new 'Perl6Pair'
+ setattribute pair, '$!key', key
+ setattribute pair, '$!value', value
+
+ .return (pair)
+
+ #.return (pair)
+.end
+
=back
=cut
|
From @jnthnOn Fri May 16 17:27:07 2008, bacek wrote:
Thanks for this. Unfortunately, this doesn't quite work; we need to Thanks, Jonathan |
The RT System itself - Status changed from 'new' to 'open' |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#54312 (status was 'resolved')
Searchable as RT54312$
The text was updated successfully, but these errors were encountered: