From recent SVN commit messages, I see that there has been some
reorganization of structure/signature matching; apologies if the reorganization is incomplete (i.e., not ready for testing) and/or the following is a known issue.
This program type checks under PolyML 5.2.1 (and SML/NJ 110.68 and MLton 20070826), but reports type errors under PolyML SVN HEAD.
===== signature UNIQUE_SET_STRUCTS = sig structure Element: sig type t end end signature UNIQUE_SET = sig include UNIQUE_SET_STRUCTS type t val toList: t -> Element.t list end structure UniqueSetRep = struct datatype 'a t = T of {elements: 'a list} end functor UniqueSet (S: UNIQUE_SET_STRUCTS): UNIQUE_SET = struct open S type elements = Element.t list structure Tree: sig structure Set: sig type t val toList: t -> elements end end = struct structure Set = struct open UniqueSetRep type t = Element.t t fun new elements = T {elements = elements} fun elements (T {elements, ...}) = elements val toList = elements end end open Tree.Set end =====
Matthew Fluet wrote:
From recent SVN commit messages, I see that there has been some
reorganization of structure/signature matching; apologies if the reorganization is incomplete (i.e., not ready for testing) and/or the following is a known issue.
I'm doing quite a bit on the compiler at the moment, committing to SVN as I'm going and haven't run the tests I would before a full release. I'm not surprised there's the occasional bug. Thanks for reporting it: I've fixed it now.
Please continue to test it and report any problems; just be prepared for things to break!
Regards, David
On Wed, 8 Apr 2009, David Matthews wrote:
Please continue to test it and report any problems; just be prepared for things to break!
OK, I will do that.
Anyway, now that you have the tracker enabled at the sourceforge site, do you prefer that channel, or shall we continue with plain email? (Right now there is only a single open/unassigned item on the tracker by myself.)
Makarius
Makarius wrote:
Anyway, now that you have the tracker enabled at the sourceforge site, do you prefer that channel, or shall we continue with plain email? (Right now there is only a single open/unassigned item on the tracker by myself.)
Phil Clayton asked the same question in a private email and I was considering how to reply. Given the low frequency of reports I wouldn't normally check Trac regularly so I think the best solution is that if you think an issue is suitable for Trac please open a ticket but also send a message to the mailing list. In theory it should be possible to configure Trac to send an email automatically but I haven't worked out how to get access to the configuration file for Trac on SourceForge. Is there anyone out there who knows about this?
David