Files
tasks/chasm/field.go
Yichao YangandGitHub cc8372d538 Chasm Interface (#6987)
## What changed?
<!-- Describe what has changed in this PR -->
- Chasm interface

## Why?
<!-- Tell your future self why have you made these changes -->
- For the new CHASM framework

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
2025-01-27 17:57:47 -08:00

106 lines
2.8 KiB
Go

// The MIT License
//
// Copyright (c) 2020 Temporal Technologies Inc. All rights reserved.
//
// Copyright (c) 2020 Uber Technologies, Inc.
//
// Permission is hereby granted, free of charge, to any person obtaining a copy
// of this software and associated documentation files (the "Software"), to deal
// in the Software without restriction, including without limitation the rights
// to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
// copies of the Software, and to permit persons to whom the Software is
// furnished to do so, subject to the following conditions:
//
// The above copyright notice and this permission notice shall be included in
// all copies or substantial portions of the Software.
//
// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
// IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
// FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
// AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
// LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
// OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
// THE SOFTWARE.
package chasm
import (
"reflect"
"google.golang.org/protobuf/proto"
)
// This struct needs to be create via reflection
// but reflection can't set prviate fields...
type Field[T any] struct {
Internal fieldInternal
}
type fieldInternal struct {
fieldType int // data, component, componentPointer
component reflect.Value
// backingNode *nodeInfo
}
func (d *Field[T]) Get(Context) (T, error) {
// remember to handle d == nil case
panic("not implemented")
}
// re. Data v.s. Component.
// Components have behavior and has a lifecycle.
// while Data doesn't and must be attached to a component.
//
// You can define a component just for storing the data,
// that may contain other information like ref count etc.
// most importantly, the framework needs to know when it's safe to delete the data.
// i.e. the lifecycle of that data component reaches completed.
func NewDataField[D proto.Message](
ctx MutableContext,
d D,
) *Field[D] {
return &Field[D]{}
}
type componentFieldOptions struct {
detached bool
}
type ComponentFieldOption func(*componentFieldOptions)
func ComponentFieldDetached() ComponentFieldOption {
return func(o *componentFieldOptions) {
o.detached = true
}
}
func NewComponentField[C Component](
ctx MutableContext,
c C,
options ...ComponentFieldOption,
) *Field[C] {
return &Field[C]{
Internal: fieldInternal{
component: reflect.ValueOf(c),
},
}
}
func NewComponentPointerField[C Component](
ctx MutableContext,
c C,
) *Field[C] {
panic("not implemented")
}
func NewDataPointerField[D proto.Message](
ctx MutableContext,
d D,
) *Field[D] {
panic("not implemented")
}
type Collection[T any] map[string]*Field[T]