No, it's very much not semantic. With nulls, a public method accepting a Foo must be prepared to deal with receiving a null-pointer for Foo. With Options, if yo

No, it's very much not semantic. With nulls, a public method accepting a Foo must be prepared to deal with receiving a null-pointer for Foo. With Options, if you declare a parameter as Foo, you've communicated that you expect a Foo, if you declare a Option<Foo>, you're prepared to accept a None.