Towel VS Refit

Towel - Throw in the towel! data structures, algorithms, mathematics, metadata, extensions, console, and more - https://github.com/ZacharyPatten/Towel

PacMan is... a PacMan clone in the console. Get the dots. Dodge the ghosts. It's not intended to be very faithful though. I didn't research the AI of the ghost, I just came up with my own AIs that worked. Here is what I did for the ghost AIs:     - Ghost a: follows you via Dijkstra Path Finding and updates every 6 frames (faster)     - Ghost b: randomly moves and updates every 6 frames (faster)     - Ghost c: follows you via Dijkstra Path Finding and updates every 12 frames (slower)     - Ghost d: randomly moves and updates every 12 frames (slower) Note: for this game I pulled in a reference to my nuget package Towel because it includes generic versions of the Dijkstra Path Finding algorithm.

Can you give an example? BCL covers the most common algorithms and data structures, so...? There's also a whole pack of additional algorithms and data structures by u/ZacharyPatten: https://github.com/ZacharyPatten/Towel

Unit Tests

Source Code

I have a GitHub project with generic data structures and algorithms here: https://github.com/ZacharyPatten/Towel It has 18 of the common comparison-based sorting algorithms.

I don't know specifically what you are looking for, but I have a project called Towel that has generic vectors. If interested: https://github.com/ZacharyPatten/Towel.

https://github.com/ZacharyPatten/Towel/blob/070d454f3fcdc5c632bf68547911718b324cf6ae/Examples/DataStructures/Program.cs#L247

Notice how algorithm #1Pool Tracking is dependent on the range of possible values while algorithm #2 Roll Tracking is not. This means if you have a relatively large range of values, then algorithm #2 is faster, otherwise algorithm #1 is faster. So if you want the most efficient method, you just need to compare those runtime complexities based on the parameters and select the most appropriate algorithm. Here is what my "Next" overload currently looks like: See Source Code Here

Here is an example if interested: https://github.com/ZacharyPatten/Towel/blob/master/Examples/CommandLine/Program.cs All I have to do is add the [Command] attribute onto the methods and call "HandleArguments".

A lot of people have given you good replies, but have you looked at Refit?

Another question that rises is, would it be better to use some HttpClient package to handle the requests, like Refit in combination with Polly. But then again, it seems Refit also uses the HttpClient factory, which was a bad thing according to the previous?

Define a Refit client interface with the following for each API endpoint, e.g. GET /foo:

Use RestEase to create your own client library. Refit is a very similar and more popular library. IMO RestEase is an improvement over Refit and I prefer it, but either will solve your problems. Both are libs that have you build interfaces describing the API endpoints, then the library handles all the boilerplate code that calls HttpClient.

Refit - simple, typed REST clients: https://github.com/reactiveui/refit

I'd advise using this https://github.com/reactiveui/refit tool for HTTP requests. It saves a lot of time for serialization, deserialization and exception handling.

Use Refit, and let manage the live of HttpClient. Also, Refit will give you a strongly typed client around an API. All you have to write is the interface. Ain't that neat ? If you can't, use the HttpClientFactory to create the HttpClient instance: https://learn.microsoft.com/en-us/dotnet/architecture/microservices/implement-resilient-applications/use-httpclientfactory-to-implement-resilient-http-requests

Use RestEase to create your own client library. Refit is a very similar and more popular library. IMO RestEase is an improvement over Refit and I prefer it, but either will solve your problems. Both are libs that have you build interfaces describing the API endpoints, then the library handles all the boilerplate code that calls HttpClient.

The controller is simple and use the Refit library to abstract the PokéAPI call and then, returns the data.

To be fair, Refit is pretty great.