On Sun, Sep 5, 2021 at 3:59 PM jake...@gmail.com <jake6...@gmail.com> wrote:
> Like Brian, I think part of he problem is possibly a miscommunication > based on "monotonically increasing". The term means that each point is > greater than, *or equal to*, the previous one. > https://en.wikipedia.org/wiki/Monotonic_function. In other words, it > never decreases. In the example given > (https://play.golang.org/p/RJbEkmFsPKM > <https://play.golang.org/p/RJbEkmFsPKM>), the capacities *are *"monotonically > increasing", as no number in the second column is smaller than the one > before it. > > If you take `f` to be a function from the array size to the capacity increase, it's not, because: 987 < 1024 but we have f(987) = 2048 and, f(1024) = 1280 That is f(987) !< f(1024) breaking monotonicity. It also breaks in the playground at the 1000 and 1100 inputs. Is it important in most programs? I don't think so. And for those programs in which it is important, chances are there are other problems you are facing way before this one rears its head. At least that would be my expectation. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAGrdgiU%3Dqxiof3TjXFeAOmGxXuvswv48TOHd%3D_z-qcubu4Cj0A%40mail.gmail.com.
