Conversation
…t, Splitter, Merger, MapNode, and Reducer classes - Added abstract Node class for defining computation nodes. - Implemented Signal class for reactive state management. - Created Memo class for memoized computations based on input changes. - Developed Effect class for side effects triggered by input changes. - Introduced Splitter class to duplicate signals into multiple outputs. - Implemented Merger class to combine multiple objects into one. - Added MapNode class for transforming input values. - Created Reducer class for accumulating state based on inputs. - Added VoidNode class for handling non-returning computations. - Established a unified Computation interface for all computation nodes. - Included examples demonstrating the usage of the new reactivity system.
- Deleted `ownership.dispose.ts`, `abstract_node.ts`, `abstract_signal.ts`, `abstract_types.ts`, `common_constants.ts`, `computation.ts`, and `tsconfig.base.json` files. - Moved and refactored `DisposalStrategy` and `batchDisposer` functions into `ownership.disposal.ts`. - Introduced `UnrolledQueue` implementation for improved performance in queue operations. - Added performance benchmarks for `UnrolledQueue`. - Updated TypeScript configuration to extend from a new base configuration. - Added new utility functions and constants for better code organization.
- Added UnrolledQueue with efficient enqueue/dequeue operations and node pooling to minimize garbage collection. - Introduced UnrolledStack interface for stack operations. - Created ReactiveNode class for representing nodes in a directed acyclic graph (DAG). - Documented Object prototype and inheritance model with optimizations. - Implemented IDisposable and IDisposableAsync interfaces for resource management. - Added assertion utility for contract validation. - Updated runtime and shared modules with documentation. - Developed comprehensive tests for ownership system and performance benchmarks for UnrolledQueue.
…source management
- Introduced `ArrowComponent` and `FunctionComponent` in the examples directory, showcasing signal usage and event handling. - Added type declarations for global constants and Reflex runtime properties in `declarations.d.ts`, enhancing type safety and clarity.
…or ownership management
…r ownership management
… for parent relationships
…README, package.json, TypeScript definitions, and source code. Add initial setup for changesets, ESLint, Prettier, and CI configuration. Create benchmark tests for ownership management and performance profiling.
…n ownership management
- Added GraphProto interface and implementation for managing reactive nodes. - Introduced utility functions for linking and unlinking observer and source links. - Created intrusive helpers for managing linked lists of sources and observers. - Developed signal primitive for reactive value management. - Implemented benchmarks and tests for graph operations and ownership management. - Removed outdated ownership test file and replaced it with a new benchmark suite.
- Removed the ownership.proto.ts file and its associated methods. - Introduced OwnershipNode class to encapsulate ownership logic with a fixed layout for better performance. - Updated ownership.scope.ts to utilize the new OwnershipNode class. - Modified ownership.type.ts to reflect changes in ownership structure. - Adjusted tests to accommodate the new ownership model and ensure functionality remains intact. - Added microbenchmarks for performance profiling of ownership operations.
…ructure graph utilities
- Moved IReactiveNode and GraphNode imports to graph.node.ts for better organization. - Updated graph benchmarks to improve readability and structure. - Simplified test cases in graph.test.ts by removing unnecessary parameters. - Added new utility functions for DOM event handling and validation. - Implemented UnrolledQueue with comprehensive benchmarks and tests for performance evaluation. - Enhanced tsconfig.json for better project structure and exclusion of unnecessary files. - Removed unused plugins directory and added README for new validation modules.
…up execution logic
- Added `compareWrap` function for comparing two numbers with a specified radius. - Introduced `CausalCoords` interface and related types for managing causal coordinates. - Defined `CausalPhase` enum to represent different phases in causal systems. - Created layout management with `FieldLayout` and `Layout64` for structured data. - Implemented packing and unpacking functions for efficient data storage. - Developed `Uint64Array` class for interleaved 64-bit storage using `Uint32Array`. - Added benchmarks and tests for `Uint64Array` to ensure performance and correctness. - Included utility functions to check runtime environment (browser, server, JSDOM).
- Deleted obsolete graph operations from `graph.operations.ts` as they are no longer needed in the new architecture. - Removed `README.md`, `object.dispose.ts`, `object.inherit.ts`, `assert.ts`, and `bitwise.ts` files that contained outdated or unused code. - Introduced new ownership context management in `ownership.context.ts` and `ownership.contract.ts` to streamline ownership handling. - Refactored `OwnershipNode` to utilize the new context management system and removed legacy ownership methods. - Updated tests to reflect changes in graph operations and ownership management.
…causal phase configuration - Updated ownership tests to utilize OwnershipService for creating and managing ownership nodes. - Removed deprecated functions and replaced them with service methods for better clarity and performance. - Enhanced benchmarks to measure performance of ownership operations with the new service. - Introduced a new file for causal phase configuration, defining enums for various causal states.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.