Implements memory profiling

[obround]

Implements per-op memory profiling to show in the herbie report.

There is a corresponding herbie branch that implements this into the report.

[pavpanchekha]

Great but has a major bug. Also check the documentation. If we document the struct we will need to 1) update the documentation and 2) bump the version number, since it's changed.

[obround]

Great but has a major bug. Also check the documentation. If we document the struct we will need to 1) update the documentation and 2) bump the version number, since it's changed.

I looked for the documentation files to update, but wasn't able to find them. Also, by bumping the version number, do you mean the version 2.2 -> 2.3 in info.rkt?:

(define collection "rival")
(define version "2.2")
(define license 'MIT)

[pavpanchekha]

The documentation is in scribblings/profile.scrbl, "Scribble" is Racket's documentation format. It's OK. It claims to describe the full struct, so we'll need to bump the version number. Yes, you found the right place.

Here's my suggestion: instead of exporting (struct-out execution), let's export only execution-name, execution-number, and so on (all the fields). That way no one can be matching on the full struct and if we add more fields in the future it'll be backwards-compatible. We should mention in the documentation that we only export field accessors, not the full struct, and then we're backwards-compatible.

[pavpanchekha]

All good on code but needs version bump, provide changes, and doc changes

[pavpanchekha]

Looks good. I would not document make-execution and otherwise if the nightlies and tests are good let's just merge.