Andrew Aladjev

This bug in flex can be fixed by declaring `rpl_malloc` and `rpl_realloc` properly in header files. But any fix will be just workaround, because bug was provided by unexpected behaviour...

I've created [the following patch](https://705800.bugs.gentoo.org/attachment.cgi?id=603698&action=diff&format=raw&headers=1) that fixes issue in dirty way (patching config.h.in). It can't be used in upstream.

Created [gentoo bug](https://bugs.gentoo.org/705800).

Hello, @Explorer09. > And since you are cross-compiling, you know how musl would behave. It means that autotools are broken by design. Nobody should know how toolchain will behave. ```...

This issue is easy to reproduce. Please do the following: ``` cd flex ./autogen.sh ./configure ac_cv_func_malloc_0_nonnull=no make cd src gcc -E -I . -DHAVE_CONFIG_H scan.c ``` Please look at "rpl_"...

Yes, you are right, so we can see the following `autoconf` design: ``` #define malloc rpl_malloc #include //#define malloc rpl_malloc - my previous wrong assumption void * rpl_malloc (size_t _)...

Hello, project authors don't want to make a new release, i don't know why too.

I've backported pr to the recent 3.0.0 beta 2 version, created the patch that can be applied on the fly using `patch-package`. [vue-multiselect+3.0.0-beta.2.patch.zip](https://github.com/shentao/vue-multiselect/files/12026252/vue-multiselect%2B3.0.0-beta.2.patch.zip)

Please be aware that bluring from descendant node requires custom `deactivate` call: ```js ``` `blur` should trigger multiselect blur together with provided event.