Search Results for "definitions"

This package makes a distinction between machine type and scientific type of a Julia object. The machine type refers to the Julia type being used to represent the object (for instance, Float64). The scientific type is one of the types defined in ScientificTypesBase.jl reflecting how the object should be interpreted (for instance, Continuous or Multiclass).

ReTest is a testing framework for Julia allowing defining tests in source files, whose execution is deferred and triggered on demand. This is useful when one likes to have definitions of methods and corresponding tests close to each other. This is also useful for code that is not (yet) organized as a package, and where one doesn't want to maintain a separate set of files for tests. Filtering run testsets with a Regex, which is matched against the descriptions of testsets. This is useful for running only part of the test suite of a package. ...

ReverseDiff is a fast and compile-able tape-based reverse mode automatic differentiation (AD) that implements methods to take gradients, Jacobians, Hessians, and higher-order derivatives of native Julia functions (or any callable object, really). While performance can vary depending on the functions you evaluate, the algorithms implemented by ReverseDiff generally outperform non-AD algorithms in both speed and accuracy.

LinearSolve.jl is a unified interface for the linear solving packages of Julia. It interfaces with other packages of the Julia ecosystem to make it easy to test alternative solver packages and pass small types to control algorithm swapping. It also interfaces with the ModelingToolkit.jl world of symbolic modeling to allow for automatically generating high-performance code. Performance is key: the current methods are made to be highly performant on scalar and statically sized small problems,...

Welcome to WhereTraits.jl. This package exports one powerful macro @traits with which you can extend Julia's where syntax in order to support traits definitions. In addition, WhereTraits comes with a standardized way how to resolve ambiguities among traits, by defining an order among the traits with @traits_order. Under the hood @traits uses normal function dispatch to achieve the speed and flexibility, however, julia function dispatch can lead to ambiguities. With traits these can easily happen if someone defines @traits for the same standard dispatch but using different traits.