Opened 8 years ago
Closed 6 years ago
#3 closed defect (fixed)
No constructors in prelude from zero_t, one_t
| Reported by: | a3moss | Owned by: | a3moss |
|---|---|---|---|
| Priority: | minor | Component: | cfa-cc |
| Version: | 1.0 | Keywords: | |
| Cc: |
Description
Do a trait assertion of the form void ?{}(T*, zero_t); (or one_t) -- int (and any other built-in type) will not satisfy it, and should.
Change History (6)
comment:2 by , 8 years ago
I think there are also no T ?=?(T*, zero_t); (that is to say, the matching assignment operators). Should these also be included in the prelude?
comment:3 by , 7 years ago
| Owner: | set to |
|---|---|
| Status: | new → assigned |
This is fixed in the resolver prototype, so whenever I integrate its assertion resolution this issue should go away.
comment:5 by , 7 years ago
| Summary: | No zero_t, one_t constructors in prelude → No constructors in prelude from zero_t, one_t |
|---|
New title is clearer
comment:6 by , 6 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
I'm not sure if the prelude library auto-generator will be smart enough to handle
zero_tandone_tthe way it should to generate these, which may be a non-trivial change.