JulianRooze

As I would like to use Jace for calculations involving money, decimal support is really important for me as well. I've begun with a really naive port of Jace where...

Well, it might be nice to do something with generics. The public API of CalculationEngine can easily be made generic: ``` csharp public interface ICalculationEngine { void AddConstant(string constantName, T...

Just a quick update on this. I went ahead and tried to make Jace work with both double as well as decimal. This is by no means a "please merge...

Agreed, so I just updated the code ;) I got rid of the duplication with the interpreter by doing what I said in my last comment. Also, I added some...

Have you had a chance to look over my suggested changes yet? :) Like I said, for us the changes I've made work perfectly fine and are 'good enough', but...

Only just noticed your response! Sorry for my late response now ;) That'd be great! I'll try to make my code ready for a pull request in the next few...

@rcl2748 the need for Jace in our application got put on the backburner, so never got around to creating a proper pull request for this, but if creating a custom...

@roji For multiple hosts + multiplexing, I assume this is not as simple as changing [this](https://github.com/npgsql/npgsql/blob/cf9d2433bc653f363705296b5804a9658bb49083/src/Npgsql/NpgsqlMultiHostDataSource.cs#L51) line to `settings.Multiplexing ? new MultiplexingDataSource`? 🙂

@vonzshik I see, something like this? https://github.com/npgsql/npgsql/compare/main...JulianRooze:npgsql:multi-host-multiplex?expand=1 Not proposing this as an actual change, just to get a feeling for the size of the change.

One thing to consider is that Npgsql considers named parameters to be legacy as they require runtime processing (conversion into positional). Using positional parameters ($1, $2, etc) is currently impossible...