fn fudge_sample_resource(&self, sample_resource: SampleResource) -> SampleResource {
        /*
         * Design thoughts:
         * * In general, I'm not a fan of "fixing" noncompliant servers: I'd rather let them fail and have
         *   that reflected in their benchmark results. Sometimes, though, I'm MORE interested in seeing
         *   their performance. This is a tricky balance to strike, and so all such hacks need to be
         *   documented in the project's `doc/server-compliance.md` file.
         */

        /*
         * Most servers are compliant, thankfully, so we provide this default no-op implementation.
         */
        sample_resource
    }
/// This is an escape hatch of sorts for non-compliant servers, which allows them to fudge/hack sample
/// data a bit, such that it can be successfully POST'd or whatnot.
///
/// Parameters:
/// * `sample_org`: a sample `Organization` JSON resource that has been generated to test this server
This is an escape hatch of sorts for non-compliant servers, which allows them to fudge/hack sample
data a bit, such that it can be successfully POST'd or whatnot.

`sample_org`: a sample `Organization` JSON resource that has been generated to test this server
This is an escape hatch of sorts for non - compliant servers which allows them to fudge / hack sample data a bit such that it can be successfully POST ' d or whatnot . ` sample_org ` : a sample ` Organization ` JSON resource that has been generated to test this server
fn fudge_sample_resource(&self, sample_resource: SampleResource) -> SampleResource {
        /*
         * Design thoughts:
         * * In general, I'm not a fan of "fixing" noncompliant servers: I'd rather let them fail and have
         *   that reflected in their benchmark results. Sometimes, though, I'm MORE interested in seeing
         *   their performance. This is a tricky balance to strike, and so all such hacks need to be
         *   documented in the project's `doc/server-compliance.md` file.
         */
        /*
         * Most servers are compliant, thankfully, so we provide this default no-op implementation.
         */
        sample_resource
    }
fn fudge_sample_resource ( & self , sample_resource : SampleResource ) -> SampleResource { /*
         * Design thoughts:
         * * In general, I'm not a fan of "fixing" noncompliant servers: I'd rather let them fail and have
         *   that reflected in their benchmark results. Sometimes, though, I'm MORE interested in seeing
         *   their performance. This is a tricky balance to strike, and so all such hacks need to be
         *   documented in the project's `doc/server-compliance.md` file.
         */ /*
         * Most servers are compliant, thankfully, so we provide this default no-op implementation.
         */ sample_resource }
This is an escape hatch of sorts for non-compliant servers, which allows them to fudge/hack sample
data a bit, such that it can be successfully POST'd or whatnot.
This is an escape hatch of sorts for non - compliant servers which allows them to fudge / hack sample data a bit such that it can be successfully POST ' d or whatnot .
&self
sample_resource
SampleResource
&self
sample_resource
SampleResource