Skip to content

libraries.md

Latest commit

 

History

History
107 lines (76 loc) · 6.72 KB

libraries.md

File metadata and controls

107 lines (76 loc) · 6.72 KB

.NET Libraries in .NET 10 Preview 3 - Release Notes

Here's a summary of what's new in .NET Libraries in this preview release:

.NET Libraries updates in .NET 10:

Introduce an AOT-Safe Constructor for ValidationContext

The ValidationContext class is used during options validation to provide validation context. Since extracting the DisplayName may involve reflection, all existing constructors of ValidationContext are currently marked as unsafe for AOT compilation. As a result, using ValidationContext in a native application build can generate warnings indicating that the type is unsafe.

To address this, we are introducing a new ValidationContext constructor that explicitly accepts the displayName as a parameter. This new constructor ensures AOT safety, allowing developers to use ValidationContext in native builds without encountering errors or warnings.

namespace System.ComponentModel.DataAnnotations;

public sealed class ValidationContext
{
    public ValidationContext(object instance, string displayName, IServiceProvider? serviceProvider = null, IDictionary<object, object?>? items = null)
}

Support for Telemetry Schema URLs in ActivitySource and Meter

OpenTelemetry defines a specification for supporting Telemetry Schemas. To align with this, the ActivitySource and Meter classes now support specifying a Telemetry Schema URL during construction.

This enhancement allows creators of ActivitySource and Meter instances to define a schema URL for the tracing and metrics data they produce. Consumers of this data can then process it according to the specified schema, ensuring consistency and compatibility.

Additionally, the update introduces ActivitySourceOptions, simplifying the creation of ActivitySource instances with multiple configuration options.

namespace System.Diagnostics
{
    public sealed partial class ActivitySource
    {
        public ActivitySource(ActivitySourceOptions options);
        
        public string? TelemetrySchemaUrl { get; }
    }

    public class ActivitySourceOptions
    {
        public ActivitySourceOptions(string name);

        public string Name { get; set; }
        public string? Version { get; set; }
        public IEnumerable<KeyValuePair<string, object?>>? Tags { get; set; }
        public string? TelemetrySchemaUrl { get; set; }
    }
}

namespace System.Diagnostics.Metrics
{
    public partial class Meter : IDisposable
    {
        public string? TelemetrySchemaUrl { get; }
    }

    public partial class MeterOptions
    {
        public string? TelemetrySchemaUrl { get; set; }
    }
}

Byte-Level Support in BPE Tokenizer

The BpeTokenizer has been available in the Microsoft.ML.Tokenizers library for some time. This update introduces support for Byte-Level encoding in the BPE tokenizer.

Byte-Level encoding allows the tokenizer to process vocabulary as UTF-8 bytes, transforming certain characters—for example, spaces are represented as Ġ. This enhancement enables the creation of tokenizer objects compatible with models that utilize Byte-Level BPE tokenization, such as the DeepSeek model. The test code demonstrates how to read a Hugging Face tokenizer.json file for DeepSeek and create a corresponding tokenizer object.

Additionally, this update introduces the BpeOptions type, making it easier to configure a BPE tokenizer using multiple options. The new factory method BpeTokenizer.Create(BpeOptions options) simplifies the instantiation process:

BpeOptions bpeOptions = new BpeOptions(vocabs);
BpeTokenizer tokenizer = BpeTokenizer.Create(bpeOptions);

Deterministic option for LightGBM Trainer in ML.NET

LightGBM is one of the most popular trainers in ML.NET. In ML.NET we expose a limited set of options to simplify its use. Unfortunately, this meant you could sometimes get non-deterministic results even with the same data and the same random seed. This is due to how LightGBM does its training.

This update exposes LightGBM's deterministic, force_row_wise, and force_cos_wise options to allow you to force deterministic training behavior when needed. You can set these options using the appropriate LightGBM options class based on which trainer type you are using.

LightGbmBinaryTrainer trainer = ML.BinaryClassification.Trainers.LightGbm(new LightGbmBinaryTrainer.Options
{
    NumberOfLeaves = 10,
    MinimumExampleCountPerLeaf = 2,
    UnbalancedSets = false,
    Deterministic = true,
    ForceRowWise = true
});

Tensor enhancements

When we initially released Tensor last year we did not provide any non-generic means of interacting with it, even for things that don't really need that generic information such as getting the Lengths and Strides. This update changes the class hierarchy by adding in a non-generic interface that allows you to do those types of operations without needing to worry about generics. It also adds the ability to get/set data in a non-generic why by boxing to type object. This does incur a performance penalty and should be avoided when performance is desired, but can make some data access easier when its not required.

When performing Slice operations on a Tensor, the initial implementation copied the underlying data. This copy could be avoided by using a TensorSpan or ReadOnlyTensorSpan, but there were many times that same behavior was desired on Tensor as well. This update adds that behavior. Now, slice operations on a Tensor perform the same as the TensorSpan types and no longer do a copy.