Swift has Optionals. C# has Nullable types. As far as I can tell both serve same purpose, besides value of some type they store information whether variable has value or is undefined (uninitialized).Question is are Optionals just Nullable types with different name or are there other conceptual differences? In another words, talking about concept itself, or in context of languages that do not have Optionals or Nullables, does it matter whict term is used? When implementing that functionality in language does it matter whether I name type Optionals<T> or Nullable<T> 
What is the difference between Optionals and Nullable type
object oriented;programming languages;terminology
There is a different connotation, even though they work very similarly.  Everyone but Microsoft (insert eye-roll here) uses null and nullable only in the context of references.  Options and Maybes are generally understood to refer to both references and values, especially in functional programming languages where referential transparency means there isn't much difference between a value and a reference.In another words, talking about concept itself, or in context of languages that do not have Optionals or Nullables, does it matter which term is used?Options is the term that causes the least confusion among a broad audience.  Only C# programmers will think of a Nullable as potentially applying to a value type, and I think most of them are at least aware of what an Option is.