[nem-bug] [Nemerle 0000990]: Class() should "return" class, not void

feedback at nemerle.org feedback at nemerle.org
Mon Oct 15 20:55:08 CEST 2007


A NOTE has been added to this issue.
======================================================================
<http://nemerle.org/bugs/view.php?id=990> 
======================================================================
Reported By:                divan
Assigned To:                
======================================================================
Project:                    Nemerle
Issue ID:                   990
Category:                   Compiler (type engine)
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
======================================================================
Date Submitted:             04-17-2007 18:32 CEST
Last Modified:              10-15-2007 20:55 CEST
======================================================================
Summary:                    Class() should "return" class, not void
Description: 
class Main {
 x : int;
 static Main () : void {
  Main ().x;
 }
}

mainmain.n:4:3:4:7: error: typing fails on ambiguity between
overloads:
mainmain.n:4:3:4:7: error: Posible overload: method
Main.Main() : void
mainmain.n:4:3:4:7: error: Posible overload: constructor
Main..ctor() : void
======================================================================

----------------------------------------------------------------------
 divan - 07-07-07 22:14 
----------------------------------------------------------------------
In fact type is ok, void->Main, it's just a bit confusing message.

Maybe we should be able to put more constraints on any TyVar (like "has
member x") and use these in delayed typing.

----------------------------------------------------------------------
 nazgul - 07-08-07 12:00 
----------------------------------------------------------------------
The description of constructor should be shown as Main..ctor () : Main 

But the real issue it as you said - lack of constraint that anything in a
'obj.member' position should not have return type void.

----------------------------------------------------------------------
 divan - 10-15-07 20:55 
----------------------------------------------------------------------
Fixed ctor.ToString on r7808.

Issue History
Date Modified  Username       Field                    Change              
======================================================================
04-17-07 18:32 divan          New Issue                                    
07-07-07 21:55 divan          Issue Monitored: divan                       
07-07-07 22:14 divan          Note Added: 0001935                          
07-08-07 12:00 nazgul         Note Added: 0001936                          
10-15-07 20:55 divan          Note Added: 0001963                          
======================================================================




More information about the bugs mailing list