Comments (6)
Yeah const
instead.
And we make traits to detect plot axis rather than inheritance like we have now.
We can also make show
nicer and not show the Dim{}
part most if the time.
from dimensionaldata.jl.
Damn thats a bug with keyword handling maybe.
Btw im thinking to delete the custom dims anyway soon and switch to just Dim...
from dimensionaldata.jl.
oh no! i find the concise syntax of custom dims nice. but, i guess it would be (syntactically) equivalent to define const Foo = Dim{:Foo}
instead of using DimensionalData.@dim Foo
, right? show
would display Dim{:Foo}
but programmatically you could still use e.g. fill(NaN, Foo(1:3, order=Unordered()))
.
from dimensionaldata.jl.
Ah this is just a macro scope issue. Will fix.
from dimensionaldata.jl.
thanks for fixing! but, i'm wondering now whether to use const
or @dim
. what are the tradeoffs? is there a discussion somewhere on your plan to remove custom dims?
from dimensionaldata.jl.
It shouldn't make much difference - I will just change the macro to create the const
definition and it will keep working with very little disruption for most things. I'm hoping e.g. Rasters.jl wont need to do anything with the update even though it uses the @dims
macro.
from dimensionaldata.jl.
Related Issues (20)
- `using DimensionalData.Lookups` in docs does not work HOT 4
- can't `cat` two empty vectors HOT 1
- Dimension labels do not plot in Makie on 0.27.0
- Use DataAPI.jl metadata function HOT 1
- Optimise selectors like `Near` and `Contains` on `Regular` lookups
- Copy of Dictionary of DimArrays creates views HOT 2
- Plot of one dimensional DimArray ignores the lookup values of the dimensions HOT 2
- Feature Request: pass fill value (single element) to `DimArray` HOT 8
- Support plot mutation with global Axis HOT 10
- Towards a nicer Makie recipe HOT 2
- Would it be useful to have Not() as a selector? HOT 3
- Makie extension throws StackOverflowError when dimensions have Unitful units HOT 4
- Dimensions of Observable(dd) are ignored in Makie 0.21 HOT 9
- Displaying one-dimensional `DimArray` does not quite work in Pluto HOT 8
- Performance of `broadcast_dims` on `DimStack` vs `DimArray` HOT 1
- Remove if VERSION checks HOT 1
- Plotting deprecations in tests
- Reduce number of warnings in tests HOT 1
- How can I create a 2D array using broadcasting? HOT 1
- MethodError: no method matching `copy(::X{LinRange{Float64, Int64}})`
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dimensionaldata.jl.