Code With Go
  • Code With Go
  • 01. What, Who, Why and Where?
  • 02. Compiled vs Interpreted languages
  • 03. Types of Type!
  • 04. Stack and Heap Memory
  • 05. Garbage Collection
  • 06. About Go
  • 07. Go Playground
  • 08. Hello, World!
  • 09. Installing Go
  • 10. Variables
  • 11. Constants
  • 12. Integers
  • 12. Floats
  • 13. Boolean
  • 14. Strings
  • 15. Complex Numbers
  • 16. If Else
  • 17. Switch
  • 18. For
  • 19. User Defined Types
  • 20. Arrays
  • 21. Slices
  • 22. Structs
  • 23. Maps
  • 24. Functions
  • 25. Defer
  • 26. Pointers
  • 27. Methods
  • Resources
    • Resources - Paid
    • Resources - Free
Powered by GitBook
On this page
  • Type System
  • Type Error
  • Type Safety
  • Strong Typing
  • Weak Typing
  • Static Type Checking
  • Dynamic Type Checking
  • Manifest Typing
  • Type Inference
  • Duck Typing
  • Blog Posts

Was this helpful?

03. Types of Type!

Because type is life!

Type System

Type system is a set of rules that assigns a property called type to the various constructs of a computer program, such as variables, expressions, functions or modules

Type Error

A type error is erroneous or undesirable program behavior caused by a discrepancy between differing data types for the program's constants, variables, and methods.

Type Safety

The extent to which a programming language discourages or prevents type errors

Strong Typing

A strongly typed language typically disallows implicit conversions between unrelated types

Weak Typing

A weakly typed language makes conversions between unrelated types implicitly

Static Type Checking

Static type checking is the process of verifying the type safety of a program based on analysis of source code.

Dynamic Type Checking

Dynamic type checking is the process of verifying the type safety of a program at run-time

Manifest Typing

Manifest typing is explicit identification by developer of the type of each variable being declared

Type Inference

Automatic detection of type based on usage.

Duck Typing

If it walks like a duck and it quacks like a duck, then it must be a duck

Blog Posts

Previous02. Compiled vs Interpreted languagesNext04. Stack and Heap Memory

Last updated 5 years ago

Was this helpful?

Understanding Type in Go
Logo