News items for previous commit

doc/manual/stmts.txt

@@ -130,9 +130,9 @@ If a proc is annotated with the ``noinit`` pragma this refers to its implicit
 
 
 The implicit initialization can be also prevented by the `requiresInit`:idx:
-type pragma. The compiler requires an explicit initialization then. However
+type pragma. The compiler requires an explicit initialization for the object
-it does a `control flow analysis`:idx: to prove the variable has been
+and all of its fields. However it does a `control flow analysis`:idx: to prove
-initialized and does not rely on syntactic properties:
+the variable has been initialized and does not rely on syntactic properties:
 
 .. code-block:: nim
   type

web/news/e031_version_0_16_2.rst

@@ -49,7 +49,13 @@ Changes affecting backwards compatibility
   instead of signed integers.
 - In Nim identifiers en-dash (Unicode point U+2013) is not an alias for the
   underscore anymore. Use underscores and fix your programming font instead.
-
+- When the ``requiresInit`` pragma is applied to a record type, future versions
+  of Nim will also require you to initialize all the fields of the type during
+  object construction. For now, only a warning will be produced.
+- The Object construction syntax now performs a number of additional safety
+  checks. When fields within case objects are initialiazed, the compiler will
+  now demand that the respective discriminator field has a matching known
+  compile-time value.
 
 Library Additions
 -----------------