diff options
author | Boris Kolpackov <boris@codesynthesis.com> | 2015-01-23 12:31:11 +0200 |
---|---|---|
committer | Boris Kolpackov <boris@codesynthesis.com> | 2015-01-23 12:31:11 +0200 |
commit | 006dd946e550a16004d4b7f62e9e026e4504cd23 (patch) | |
tree | 52eabb6c027329a57f0daf1c40be120212dacbb9 /feature/list | |
parent | 52785dde4b58f2edacdccf7d8557fdf41cb33781 (diff) |
Diagnose lack of default constructor in pointed-to objects
Lack of the default constructor will lead to uncompilable generated code.
Diffstat (limited to 'feature/list')
-rw-r--r-- | feature/list | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/feature/list b/feature/list index 688c9f0..18ae045 100644 --- a/feature/list +++ b/feature/list @@ -16,12 +16,6 @@ This could be very useful in data migration code. In fact, need to add an example in the manual when this is supported. -! Diagnose lack of default ctor if object used in relationship - - Got two questions on the mailing list about that in one week. Maybe - always diagnose lack of public ctor? Maybe with a warning if no - relationship? The no_ctor pragma like no_id? - ? Duplicate columns It can sometimes be useful to map multiple data members to the same |