Are there still reasons to use lazy_static?

Question

lazy_static is a very popular crate. Years ago it had no better alternatives for certain tasks. But today, are there still any reasons to choose lazy_static over the newer once_cell or the upcoming LazyLock?

score 5 · Answer 1 · answered Sep 19 '22 at 17:31

5

If you'd like to support #![no_std] platforms, you may still prefer to use lazy_static. As per the once_cell documentation :

Unlike once_cell, lazy_static supports spinlock-based implementation of blocking which works with #![no_std].

answered Sep 19 '22 at 17:31

antonok

516
6
9

score 4 · Answer 2 · edited Aug 12 '22 at 10:06

4

once_cell and LazyLock have a minimum support version of the compiler. For earlier versions of it you would probably want to stick to lazy_static which has served it purpose pretty well when less features were available.

edited Aug 12 '22 at 10:06

thatfellowoveryonder

301
3
13

answered Oct 10 '21 at 11:24

Netwave

40,134
6
50
93

Are there still reasons to use lazy_static?

2 Answers2