Skip to content

Add documentation for Software Transactional Memory (STM) in Effect#1111

Open
sharno wants to merge 2 commits into
Effect-TS:mainfrom
sharno:add-stm
Open

Add documentation for Software Transactional Memory (STM) in Effect#1111
sharno wants to merge 2 commits into
Effect-TS:mainfrom
sharno:add-stm

Conversation

@sharno

@sharno sharno commented Apr 7, 2025

Copy link
Copy Markdown

Type

  • Refactor
  • Feature
  • Bug Fix
  • Optimization
  • Documentation Update

Description

Adding documentation for STM

Related

  • Related Issue #
  • Closes #

@vercel

vercel Bot commented Apr 7, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
website-content ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 9, 2025 1:51am
website-landing ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 9, 2025 1:51am
website-proxy ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 9, 2025 1:51am

@vercel

vercel Bot commented Apr 7, 2025

Copy link
Copy Markdown

@sharno is attempting to deploy a commit to the Effect Team on Vercel.

A member of the Team first needs to authorize it.

@suddenlyGiovanni

suddenlyGiovanni commented Apr 7, 2025

Copy link
Copy Markdown
Contributor

👏🏻 Wow, well done!

Minor nitpicking: According to @ethanniser's workshop, code within the scope of STM should be "pure." Would it be a good idea to draw the user's attention to this constraint?

References:

@IMax153

IMax153 commented Apr 7, 2025

Copy link
Copy Markdown
Member

cc @mikearnaldi for a review here

@IMax153 IMax153 requested a review from mikearnaldi April 7, 2025 12:53
@sharno

sharno commented Apr 7, 2025

Copy link
Copy Markdown
Author

Minor nitpicking: According to @ethanniser's workshop, code within the scope of STM should be "pure." Would it be a good idea to draw the user's attention to this constraint?

References:

Thank you! If the idea of adding the STM page is generally accepted I can add more details from this workshop

@mikearnaldi

Copy link
Copy Markdown
Member

Minor nitpicking: According to @ethanniser's workshop, code within the scope of STM should be "pure." Would it be a good idea to draw the user's attention to this constraint?
References:

Thank you! If the idea of adding the STM page is generally accepted I can add more details from this workshop

yes I'd be totally in favour of adding an STM page to the docs

… importance in transactional memory. Include examples demonstrating the pitfalls of using mutable data structures within `TRef`s, and introduce additional STM data structures for better state management.
@sharno

sharno commented Apr 9, 2025

Copy link
Copy Markdown
Author

@mikearnaldi @suddenlyGiovanni

Sweet!
I added a section about immutability
Also a section about other Transactional DSs

I think this is ready if you don't see other issues

@sharno

sharno commented Jun 9, 2025

Copy link
Copy Markdown
Author

Any chance to review this to get it merged?

@suddenlyGiovanni

Copy link
Copy Markdown
Contributor

Any chance to review this to get it merged?

I know the primary focus is on "SMOL", but do we have any updates on this one @mikearnaldi?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants