Skip to content
This repository
Browse code

Remove questions.txt in favor of Github's issue tracker.

The one unanswered question from questions.txt is now at
#17 .
  • Loading branch information...
commit aca4dff4da8f83c8ca329f83c8914e03d979472d 1 parent 70c1b24
Patrick R. Michaud authored July 07, 2012

Showing 1 changed file with 0 additions and 41 deletions. Show diff stats Hide diff stats

  1. 41  questions.txt
41  questions.txt
... ...
@@ -1,41 +0,0 @@
1  
-This file contains miscellaneous questions about design and
2  
-specification that implementors have come up with that are
3  
-awaiting answers from Larry (TimToady) and/or others.
4  
-Answers are recorded here as well, but are moved into a
5  
-lower section of the file to keep the as-yet unanswered 
6  
-questions on top.  It's like an absurdly simple ticket system.
7  
-
8  
-(See https://github.com/perl6/mu/blob/master/misc/pm.txt for
9  
-a previous incarnation of this file.)
10  
-
11  
-As yet unanswered questions:
12  
-
13  
-Q1: (pmichaud) Does numifying or stringifying a type object
14  
-    produce an immediate 'warn' or a Failure?  What's the
15  
-    expected result from:
16  
-
17  
-        my $x;
18  
-        my $y = +$x;
19  
-        say 'alive';
20  
-        say $y;
21  
-
22  
-    Is the warning generated at the point of assignment to $y
23  
-    or at the point where $y is used?
24  
-
25  
-
26  
-Q2: (pmichaud) What's the expectation of how "useless use of '+'
27  
-    in sink context" messages will be generated?  Are they
28  
-    generated at compile-time based on a trait of the (proto) sub,
29  
-    or is it something that &infix:<+> would detect and carp
30  
-    about at runtime?
31  
-
32  
-A2: (moritz) They are generated at compile-time based on a trait
33  
-    on the proto sub.
34  
-    Reasons are:
35  
-    * The user wants a warning per occurence in the source code,
36  
-      not per call
37  
-    * performance considerations
38  
-    See also: http://irclog.perlgeek.de/perl6/2012-02-17#i_5161470
39  
-
40  
-
41  
-Pm

0 notes on commit aca4dff

Please sign in to comment.
Something went wrong with that request. Please try again.