yip.c | YAML Incremental Parser in C | YAML Processing library

verify=False is a one way of doing it, but a better way to disable those warnings is to use this:

A function that's constexpr means that the function potentially can be evaluated at compile-time. The function must however also be callable with a run-time value, and produce a run-time result.

A variable that's constexpr has to be a compile time constant. Period.

What that means for your validateIP function is that you don't need to make count constexpr. You can write a function and mark it as constexpr.

When you call the function with a compile time constant, it will get evaluated at compile time.

If you call it with a run time value it will get evaluated at run time.

You should be checking some more stuff in the response you get. The IRestResponse instance gives you quite a lot of information about what happened. RestSharp doesn't throw exceptions by design and any errors that occurred during the request execution would result in the response code 0 and the exception itself is added to the response object.

We have documented this behaviour. There are a bunch of other properties that you can use to find out the actual response code and any errors.

You can also set the client ThrowOnAnyError property to true to force RestSharp to throw.