nickorlow

they're working on something similar to this, called profiles

I wouldn't think of Pittsburgh as a place where car free living is popular. It is in Philadelphia, however

yes

due to how hard it is to change the networks, I think there's a lot of inefficient route design. if you look at SEPTA in Philadelphia, they're in the middle of realigning a lot of their bus routes for the first time in 60 yrs and ridership has increased noticeably since they started.

> Frequency ranged from 7.5 minutes to 15 minutes, so these came often enough that people could just go out and wait for them, not worrying about a schedule'

If only most cities could have this today

You mean the Android subsystem for iOS?

I wonder how they landed on 16.5

I guess they ran out of numbers?

My point was that contracts as defined in the standard today aren't evaluated in this manner.

The consequence of not being required in the standard is that compilers may not implement it and if they do, they will likely have different implementations/functionality

Yes, though that wouldn't be consistent w/ the standard

Profiles should (hopefully) rein this in by getting people to start subsetting language features in their codebases

> They can be compile time if the compiler can verify them statically (where they become a noop)

This only happens during constant evaluation. For example, the following could be determined statically, but compiles w/o error on gcc

int add_nums(int x, int y)

    pre(x >= 0)

    pre(y >= 0)

{

    return x + y;

}

int result_rt = add_nums(-1,-1); // no compile error