mirrors/Nim
1
0
Fork 0
mirror of https://github.com/nim-lang/Nim.git synced 2026-05-05 13:34:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

fixes #21245; warn about destructors that can raise (#21726)

Browse Source 
* fixes #21245; warn about destructors that can raise

* doc update

* progress

* typo

(cherry picked from commit 220b450489)
This commit is contained in:
Andreas Rumpf
2023-04-26 22:32:10 +02:00
committed by narimiran
parent ae83058be2
commit 4fc22cdd4d
3 changed files with 18 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
doc/destructors.rst
View File

@@ -13,12 +13,12 @@ Nim Destructors and Move Semantics
About this document
===================
This document describes the upcoming Nim runtime which does
This document describes the ARC/ORC Nim runtime which does
not use classical GC algorithms anymore but is based on destructors and
move semantics. The new runtime's advantages are that Nim programs become
move semantics. The advantages are that Nim programs become
oblivious to the involved heap sizes and programs are easier to write to make
effective use of multi-core machines. As a nice bonus, files and sockets and
the like will not require manual `close` calls anymore.
the like can be written not to require manual `close` calls anymore.
This document aims to be a precise specification about how
move semantics and destructors work in Nim.
@@ -134,6 +134,14 @@ The general pattern in `=destroy` looks like:
freeResource(x.field)
A `=destroy` is implicitly annotated with `.raises: []`; a destructor
should not raise exceptions. For backwards compatibility the compiler
produces a warning for a `=destroy` that does raise.
A `=destroy` can explicitly list the exceptions it can raise, if any,
but this of little utility as a raising destructor is implementation defined
behavior. Later versions of the language specification might cover this case precisely.
`=sink` hook
------------