# \#properties

**URL:** https://discourse.julialang.org/tag/properties/1549.md

[Latest](https://discourse.julialang.org/latest.md) · [Categories](https://discourse.julialang.org/categories.md) · [Tags](https://discourse.julialang.org/tags.md)

---

## [Struct with read-only and write-only properties](https://discourse.julialang.org/t/struct-with-read-only-and-write-only-properties/129179)

<div class="topic-metadata">

**Author:** [@mattsignorelli](https://discourse.julialang.org/u/mattsignorelli)\
**Replies:** 7\
**Last updated:** [May 21, 2025, 7:15pm UTC](https://discourse.julialang.org/t/struct-with-read-only-and-write-only-properties/129179 "2025-05-21T19:15:16Z")

</div>

Suppose I have the following mutable struct @kwdef mutable struct Rectangle{T} x::T = 0 y::T = 0 function Rectangle(args...) return new{promote\_type(typeof.(args)...)}(args...) end end I would like for this…

---

## [Unsure about properties](https://discourse.julialang.org/t/unsure-about-properties/110756)

<div class="topic-metadata">

**Author:** [@sadish-d](https://discourse.julialang.org/u/sadish-d)\
**Replies:** 11\
**Last updated:** [February 26, 2024, 3:34pm UTC](https://discourse.julialang.org/t/unsure-about-properties/110756 "2024-02-26T15:34:10Z")

</div>

I like the syntax of properties, like that they’re not the same as fields, and that I don’t have to export them. I’m considering switching from using accessor functions to properties in a large chunk of code, but I’m not…