From 006dd946e550a16004d4b7f62e9e026e4504cd23 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Fri, 23 Jan 2015 12:31:11 +0200 Subject: Diagnose lack of default constructor in pointed-to objects Lack of the default constructor will lead to uncompilable generated code. --- reference/feature/list | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 reference/feature/list (limited to 'reference') diff --git a/reference/feature/list b/reference/feature/list new file mode 100644 index 0000000..2cc3e8a --- /dev/null +++ b/reference/feature/list @@ -0,0 +1,10 @@ ++ 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? + + For now only diagnose (error) for pointed-to objects since that + will lead to uncompilable generated code (as opposed to user + code). Another option would be to add an option to warn about + the lack of default ctor in all persistent classes. \ No newline at end of file -- cgit v1.1