dtor 1.0.2

Global, no_std-compatible destructors for all platforms that run after main (like C/C++ __attribute__((destructor)))
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118

# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [1.0.2] - 2026-05-08

### Added

- Support for UEFI targets (`.fini_array` matching gnu-efi)
- Fallback to `.fini_array` for unsupported targets (with a warning)

### Changed

- `target_vendor = "pc"` is now `target_os = "windows"`. This should be a
  strictly increasing set of support for windows targets.

## [1.0.1] - 2026-05-07

### Changed

- OpenBSD support uses `method = at_module_exit` rather than `method = linker`
  by default due to C library inconsistencies. When using `method = linker`,
  the `link_section` is now `.dtors` rather than `.fini_array`.
- Documentation improvements.

## [1.0.0] - 2026-05-03

### Changed

- Stabilized (yay!). Functionally identical to 0.14.1. Thanks to all the
  contributors who helped along the way! Please file any upgrade issues in
  <https://github.com/mmastrac/linktime/issues>.
- For those upgrading from earlier versions, the major changes for you to note
  are:
    - `#[dtor(unsafe)]` is now required for `#[dtor]` items. If you are building a
      binary, you can use `RUSTFLAGS="--cfg linktime_no_fail_on_missing_unsafe"`
      (or alternatively, specify this in your `config.toml` file) to bypass the
      error.
    - For those re-exporting `dtor` from their own crates: the
      `dtor::declarative::dtor!` macro should be preferred over
      `#[dtor(crate_path = ...)]`. The latter form will continue to work, but
      the declarative macro is far more stable for most use cases. See
      <https://docs.rs/dtor/latest/dtor/declarative/macro.dtor.html> for more
      details.

## [0.14.1] - 2026-05-04

### Changed

- `wasm32-unknown-unknown` would run dtor items on each call of an exported
  function.

## [0.14.0] - 2026-05-03

### Fixed

- WASM support now uses `atexit` on all platforms (including
  `wasm32-unknown-unknown`).
- Typos and other documentation nits.

## [0.13.1] - 2026-05-02

### Changed

- Documentation polish and typo fixes.

## [0.13.0] - 2026-05-02

### Changed

- `used_linker` feature moved to `--cfg linktime_used_linker` flag.

## [0.12.0] - 2026-04-30

### Added

- Support for `#[dtor]` on `impl` items. To be valid, the `fn` must have no
  `self` parameter and must not access any generic parameters from the outer
  item.
- Added `life before main` documentation to all crates.

### Removed

- Removed support code for `ctor`'s deprecated `dtor` macros.

## [0.11.0] - 2026-04-28

### Added

- Added `method` attribute to `dtor` macro.
- Added `link_section` and `export_name_prefix` attributes to `dtor` macro.
- AIX support for `ctor`/`dtor` crates.

### Changed

- Significant rewrite to ctor/dtor macros and documentation.
- Renamed `at_library_exit` to `at_module_exit` in `dtor` crate.
- Macro attributes and crate features are auto-documented.

### Removed

- `cxa_atexit` feature from `dtor` crate. (appropriate method is now used per-platform)
- `export_native` feature from `dtor` crate. (natives always exported)

## [0.8.1] - 2026-04-22

### Added

- Included licenses in all files.
- Bumped proc-macro dependency versions.
- `dtor` crate exports `native` module with `at_binary_exit` and `at_library_exit` functions.

### Fixed

- Various hardening fixes under Miri.