Anton Firszov

@JackSteel97 you can use this code to produce a rounded rectanle path: https://github.com/SixLabors/Samples/blob/38faba5caf866c0168ea67a5e7c37c06d3043775/ImageSharp/AvatarWithRoundedCorner/Program.cs#L72-L91 Then use one of the overloads in `DrawPathExtensions` to draw it: https://docs.sixlabors.com/api/ImageSharp.Drawing/SixLabors.ImageSharp.Drawing.Processing.DrawPathExtensions.html#SixLabors_ImageSharp_Drawing_Processing_DrawPathExtensions_Draw_IImageProcessingContext_SixLabors_ImageSharp_Drawing_Processing_IPen_SixLabors_ImageSharp_Drawing_IPath_

#### Positioning the new rectangle You can transform `IPathCollection` with [`IPathCollection.Transform`](https://docs.sixlabors.com/api/ImageSharp.Drawing/SixLabors.ImageSharp.Drawing.IPathCollection.html#SixLabors_ImageSharp_Drawing_IPathCollection_Transform_System_Numerics_Matrix3x2_). Use it in tandem with [`Matrix3x.CreateTranslation`](https://docs.microsoft.com/en-us/dotnet/api/system.numerics.matrix3x2.createtranslation?view=net-5.0#System_Numerics_Matrix3x2_CreateTranslation_System_Numerics_Vector2_) #### Fill the rectangle Sorry second link was wrong in my previous comment....

Not realistic for 1.0. (Edit: having troubles clicking the right button 😄 )

An `unmanaged` type constraint can "leak up" to the public API. In case of ImageSharp: the pixel types have the `unmanaged` constraint for internal reasons, and the high level `Image`...

@teo-tsirpanis https://github.com/dotnet/vblang/issues/300#issuecomment-926130290 is not a solution for the problem if the `unsafe` constraint comes from a 3p API. IMO VB users are less likely to need `sizeof` in their own...

@tgjones > in the applications I've built with Gemini, th application code far outweighs any IoC costs. Ok, but if my of my own (non Gemini-specific) application logic is IoC-intensive,...

I don't think it's worth the efforts at this point. Feels like a rabbit hole: exciting, but maybe less critical from the POV of product adoption rates. Most of the...

Having arrays of `struct`-s + a generic `SimpleMemory` (of structs) would be very handy for image processsing applications. I guess you need to follow some alignment rules on the hardware,...

We should only merge this if we are absolutely sure this is the way forward and we are ready to migrate our entire T4 logic to source generators, especially the...

> In your case instead, there's no introspection being done This is how we implemented stuff with T4, but *in theory* it would be more robust if we could enumerate...