Given that I think chpl_taskID_t's are an implementation-oriented type and not generally available to the user (correct?), this seems OK to me; alternatively, we could put in a where clause that asserts that it's being cast to int(64) only...
-Brad On Tue, 8 Jul 2014, Greg Titus wrote: > > On Tue, 8 Jul 2014, Greg Titus wrote: >> On Tue, 8 Jul 2014, Brad Chamberlain wrote: >>> Looking at the uses to determine why [_isPrimitiveType is defined to >>> return true for types that have a singleton value associated with >>> them] ... seems to turn up the following cases: >>> >>> ... >>> >>> * casts of task IDs (ChapelTaskTable.chpl): I'm having trouble believing >>> that this really wants/needs to be supported for all primitive types, >>> but can't think how this code path is exercised offhand... >> >> I don't see how it's used, either. I'll try removing it and see what >> happens. > > Very limited testing indicates that if I just take the where-clause off > of the declaration of proc _cast things work properly. (If I remove the > proc entirely I get an error about a cast from chpl_taskID_t to int(64) > in DefaultAssociative.chpl, but in retrospect I should have expected > something along those lines.) > > greg > ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
