Nullable type

From HandWiki
Revision as of 19:53, 6 February 2024 by Sherlock (talk | contribs) (url)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Short description: Feature of some programming languages

Nullable types are a feature of some programming languages which allow a value to be set to the special value NULL instead of the usual possible values of the data type. In statically typed languages, a nullable type is an option type[citation needed], while in dynamically typed languages (where values have types, but variables do not), equivalent behavior is provided by having a single null value.

NULL is frequently used to represent a missing value or invalid value, such as from a function that failed to return or a missing field in a database, as in NULL in SQL. In other words NULL is undefined.

Primitive types such as integers and Booleans cannot generally be null, but the corresponding nullable types (nullable integer and nullable Boolean, respectively) can also assume the NULL value.[jargon][citation needed] This can be represented in ternary logic as FALSE,NULL,TRUE as in three-valued logic.

Example

An integer variable may represent integers, but 0 (zero) is a special case because 0 in many programming languages can mean "false". Also this doesn't give us any notion of saying that the variable is empty, a need for which occurs in many circumstances. This need can be achieved with a nullable type. In programming languages like C# 2.0, a nullable integer, for example, can be declared by a question mark (int? x).[1][2]:46 In programming languages like C# 1.0, nullable types can be defined by an external library[3] as new types (e.g. NullableInteger, NullableBoolean).[4]

A Boolean variable makes the effect more clear. Its values can be either "true" or "false", while a nullable boolean may also contain a representation for "undecided". However, the interpretation or treatment of a logical operation involving such a variable depends on the language.

Compared with null pointers

In contrast, object pointers can be set to NULL by default in most common languages, meaning that the pointer or reference points to nowhere, that no object is assigned (the variable does not point to any object). Nullable references were invented by C. A. R. Hoare in 1965 as part of the Algol W language. Hoare later described his invention as a "billion-dollar mistake".[5] This is because object pointers that can be NULL require the user to check the pointer before using it and require specific code to handle the case when the object pointer is NULL.

Java has classes that correspond to scalar values, such as Integer, Boolean and Float. Combined with autoboxing (automatic usage-driven conversion between object and value), this effectively allows nullable variables for scalar values.[citation needed]

Compared with option types

Nullable type implementations usually adhere to the null object pattern.

There is a more general and formal concept that extend the nullable type concept, it comes from option types, which enforce explicit handling of the exceptional case.

Language support

The following programming languages support nullable types.

Statically typed languages with native null support include:

Statically typed languages with library null support include:

Dynamically-typed languages with null include:

  • Perl scalar variables default to undef and can be set to undef.
  • PHP with NULL type and is_null() method, native nullable type in version 7.1 [11]
  • Python has the None value.[12]
  • Julia has the nothing value (which is of type Nothing) and the Union{T, Nothing} type idiom.[13]
  • Ruby with nil value and NilClass type.
  • JavaScript has a null value

See also

References

  1. ↑ "Nullable Types (C#)". Msdn.microsoft.com. http://msdn.microsoft.com/en-us/library/1t3y8s4s(VS.80).aspx. Retrieved 2013-08-19. 
  2. ↑ 2.0 2.1 Skeet, Jon (23 March 2019). C# in Depth. Manning. ISBN 978-1617294532. 
  3. ↑ "(luKa) Developer Zone - NullableTypes". Nullabletypes.sourceforge.net. http://nullabletypes.sourceforge.net/. Retrieved 2013-08-19. 
  4. ↑ "NullableTypes". Nullabletypes.sourceforge.net. http://nullabletypes.sourceforge.net/onlinedoc-v1.2/. Retrieved 2013-08-19. 
  5. ↑ Tony Hoare (2009). "Null References: The Billion Dollar Mistake". QCon London. http://www.infoq.com/presentations/Null-References-The-Billion-Dollar-Mistake-Tony-Hoare. 
  6. ↑ "Optional Type - Ballerina Programming Language". https://ballerina.io/learn/by-example/optional-type.html. 
  7. ↑ BillWagner. "Nullable value types - C# reference" (in en-us). https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/builtin-types/nullable-value-types. 
  8. ↑ "Sound null safety | Dart". https://dart.dev/null-safety. 
  9. ↑ "Null Safety - Kotlin Programming Language". https://kotlinlang.org/docs/reference/null-safety.html. 
  10. ↑ KathleenDollard. "Nullable Value Types - Visual Basic" (in en-us). https://docs.microsoft.com/en-us/dotnet/visual-basic/programming-guide/language-features/data-types/nullable-value-types. 
  11. ↑ "PHP: RFC:nullable_types". https://wiki.php.net/rfc/nullable_types. 
  12. ↑ "Built-in Constants — Python 3.9.5 documentation". https://docs.python.org/3/library/constants.html#None. 
  13. ↑ "Types · the Julia Language". https://docs.julialang.org/en/v1/manual/types/#Type-Unions. 



Retrieved from "https://handwiki.org/wiki/index.php?title=Nullable_type&oldid=3376524"