rust VS DefinitelyTyped

You can use Tensorflow for Rust to simplify that task and avoid pain with regex. Just have the right mindset.

What is the benefit of this compared to using bindings/a wrapper to Tensorflow, or other ML libraries written in C/C++, such as this community hosted project on tensorflow's github. If it's just for fun that is a valid enough reason imo, just curious since you describe it as a better Tensorflow because of the typing vs using the python wrapper, when there already exist ways to interact with tensorflow with both Rust and other statically typed languages, also including C++ (officially supported), C#, Haskell and Scala, as well as probably having bindings not mentioned on the documentation for more niche languages.

(3) You could use TensorFlow as your executor: https://github.com/tensorflow/rust

TensorFlow has language support for TypeScript well as Rust.

Thank you for the restponse! With tensorflow I am probably better of with something like; [tensorflow rust bindings](https://github.com/tensorflow/rust/tree/master/src). But I believe some useful extensions are still written in python for example; [TFDV](https://github.com/tensorflow/data-validation).. and how about scikit-learn or even something that is simpler like fb-prophet that is entirely written in python?

Tensorflow bindings exist, technically, but they're in a pretty rough state AFAIK.

tensorflow/rust (Rust): Rust language bindings for TensorFlow

Prior to React 18, it used to include an implicit children prop, making it suitable for components expected to have children. For a long time, though, the implicit children prop type has been removed according to React 18's type changes.

Additionally, because TypeScript has a well established and widely used install-base, there are already many different definition files in the wild for supporting non-TypeScript supporting projects. One of the more extensive collections of these typings lives at the DefinitelyTyped repository, which publishes the package's community typings under the package names @types/your-package-name (where your-package-name is the name of the project you're looking for typings of) that you can look for on your package manager.

View on GitHub

Firefox maintain a library for unified extension API https://github.com/mozilla/webextension-polyfill

Their type definition for HAR request isn't exported https://github.com/DefinitelyTyped/DefinitelyTyped/blob/mast...

type NumberOrString = number | string; type Status = "idle" | "loading" | "success" | "failure" // React useState, can receive a value or a function as parameter to serve as initial value. // https://github.com/DefinitelyTyped/DefinitelyTyped/blob/a03856975a17eba524739676affbf70ac4078176/types/react/v17/index.d.ts#L920 function useState(initialState: S | (() => S)): [S, Dispatch>];

The TypeScript pull request was merged, so Sebastian (who helps maintain the React type definitions) exercised new powers in this pull request to the DefinitelyTyped repository for the React type definitions. At the time of writing, this pull request is still open, but once merged and shipped the React community we will feel its benefits.

there is an open issue: https://github.com/DefinitelyTyped/DefinitelyTyped/issues/61616

Relatively infrequently. Normally, if an npm package is popular and doesn’t have its own types, there will be a community provided types declaration file available from https://github.com/DefinitelyTyped/DefinitelyTyped