Xuanwo
For instance, DataFusion is attempting to use arrow-udf as seen at https://github.com/apache/datafusion/pull/11488, which has a MSRV of 1.76. I don't want to break their progress.
> Yes, we can wait until apache/datafusion#11690 is merged. Sorry, please allow me to make it more clear: I think we should wait for our users change their MSRV to...
> Any updates on this PR? I think we now have 1.84 released, and datafusion's MSRV is 1.81 now. Makes sense, let's go.
cc @PsiACE do you want to resolve the conflicts here?
> The version is locked to `hyper = "=1.1.0"` by package `deno_http v0.141.0` Does anyone actually use our deno support?
Let's close this PR first.
> It's just that bit-vec released a new version deno specify `bit-vec = "0"` ...
cc @wangrunji0408, #39 is the temp workaround. To fully address this, we need either: - A. Wait for deno bumps all it's dpendences with correct version instead of `0` -...
Reopen to continue the discussion.
Yes, I feel the same way; maintaining deno support for arrow-udf isn't worth it unless we have users.