enso-org/enso
1
1
Fork 0
mirror of https://github.com/enso-org/enso.git synced 2024-11-24 00:27:16 +03:00
Code Issues Projects Releases Wiki Activity
9ae4b24d85
enso/CHANGELOG.md

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

1708 lines
85 KiB
Markdown
Raw Normal View History

Prepare for next development cycle. Original commit: https://github.com/enso-org/ide/commit/2493dcd1dc7cac03bc2693feac219cdeb379ab8e
2021-10-17 23:56:49 +03:00
# Next Release
Colorful Histograms (#3153)
2021-11-18 17:17:38 +03:00
#### Visual Environment
Pan camera to created nodes. (#3552) If a node created by the user gets placed off-screen, the screen's camera is panned to make the node visible. https://www.pivotaltracker.com/story/show/181188687 #### Visuals A screencast showing a number of node creation scenarios when the camera is panned to the newly created node, including when zoomed out. https://user-images.githubusercontent.com/273837/177169716-50a12b0a-c742-4b01-9766-56206e7938b9.mov # Important Notes - Camera is panned also if the node is only partially visible, or if there's not enough free space visible around the node. The specific amount of free space that needs to be visible around a newly created node is configured in the theme. - If the screen area is so small that the node cannot be fully fit in it (either horizontally or vertically), showing the left and top boundaries of the node's area takes priority over showing the corresponding opposite edges.
2022-07-06 13:33:35 +03:00
- [Camera is panned to newly created nodes.][3552]
Component Group View with static header and without icons (#3373) Add an initial version of the visual component for displaying the Component Group View. The component contains a header (for displaying the Group Name) and a list of labels (for displaying the component names). https://www.pivotaltracker.com/story/show/181724889 #### Visuals A screenshot from a debug scene demonstrating the component: <img width="251" alt="Screenshot 2022-04-13 at 20 07 56" src="https://user-images.githubusercontent.com/273837/163243304-21c3ad78-4813-4368-b3bb-844d979da699.png"> Screenshots from other debug scenes (`list_view` and `text_area`), demonstrating that the other components still display correctly: <img width="202" alt="Screenshot 2022-04-13 at 20 08 56" src="https://user-images.githubusercontent.com/273837/163243428-de9dc1c7-5a9f-45e0-9325-db60cece9768.png"> <img width="403" alt="Screenshot 2022-04-13 at 20 08 48" src="https://user-images.githubusercontent.com/273837/163243432-895061d9-5bd9-4349-8679-eb63b0f6724d.png"> A screenshot of the Node Searcher's list, showing that long entries in a ListView are now truncated, and an ellipsis character is added in place of removed characters: <img width="651" alt="Screenshot 2022-04-13 at 20 10 16" src="https://user-images.githubusercontent.com/273837/163243664-5b671969-7aa0-4bef-8fd2-825602d85848.png"> # Important Notes - Adding support for the text truncation feature in `ListView` required some changes in the`list_view::Entry`-related APIs. - An embedded font was added (DejaVuSans-Bold) for use in the Component Group View debug scene, and 5 unused embedded fonts were removed.
2022-04-14 13:37:40 +03:00
- [Long names on the Node Searcher's list are truncated.][3373] The part of the
name that doesn't fit in the Searcher's window is replaced with an ellipsis
character ("…").
Applying Magnet Alignment Algorithm to newly opened Component Browser (#3366) [Task link](https://www.pivotaltracker.com/story/show/181076594) This PR enables new node position adjustment using the Magnet Alignment algorithm for the following cases: - When creating node with (+) button without nodes selected - When creating node with "Mouse pointer dictated placement." not under the source node - When the node is pushed left due to lack of space - only horizontally The size of the `alignment area` around node is slightly enlarged, so that it's impossible to create a node that is being too close to other nodes. Videos with AC demonstration: https://user-images.githubusercontent.com/6566674/160565491-818b1705-43f8-41ab-abad-047031b2f9e5.mp4 https://user-images.githubusercontent.com/6566674/160565501-d2d4ea85-68c7-4385-9681-701ab86fdd98.mp4 https://user-images.githubusercontent.com/6566674/160565535-9cbeadfe-397b-4cf8-802a-1ec4148a70a2.mp4
2022-04-05 14:22:29 +03:00
- [Magnet Alignment algorithm is used while placing new nodes][3366]. When we
find an available free space for a new node, the node gets aligned with the
surrounding nodes horizontally and vertically. This helps to preserve a nice
grid-like layout for all the nodes.
Placement of newly opened Component Browser when nodes are selected (#3361) When a new node is created with the <kbd>TAB</kbd> key or by clicking the `(+)` on-screen button while multiple nodes are selected, place the new node below all the selected nodes. (Previously, the new node was placed below the node that was selected earliest.) Additionally, when placing a new node below an existing non-error node with a visualization enabled, place the new node below the visualization. (Previously, the new node was placed to the left of the visualization.) https://www.pivotaltracker.com/story/show/180887079 #### Visuals The following screencast demonstrates the feature on various arrangements of selected nodes, with visualization enabled and disabled. https://user-images.githubusercontent.com/273837/159971452-148aa4d7-c0f3-4b48-871a-a2783989f403.mov The following screencast demonstrates that new nodes created by double-clicking an output port of a node with visualization enabled are now placed below the visualization: https://user-images.githubusercontent.com/273837/160107733-e3f7d0f9-0161-49d1-8cbd-06e18c843a20.mov # Important Notes - Some refactorings that were needed for this PR were ported from the #3301 PR: - the code responsible for calculating the positions of new nodes was moved to a separate module (`new_node_position`); - the `free_place_finder` module was made a submodule of the `new_node_position` module, due to the latter being its only user.
2022-03-31 23:17:04 +03:00
- [Nodes created via the <kbd>TAB</kbd> key or by clicking the (+) button on the
screen are now placed below all the selected nodes when more than one node is
selected.][3361] (Previously, they were placed below the first node that was
selected.) This makes it easier to achieve a compact, vertical layout of the
graph.
Placement of newly opened Component Browser dictated by the mouse pointer. (#3301) Use a new algorithm for placement of new nodes in cases when: - a) there is no selected node, and the `TAB` key is pressed while the mouse pointer is near an existing node (especially in an area below an existing node); - b) a connection is dragged out from an existing node and dropped near the node (especially in an area below the node). In both cases mentioned above, the new node will now be placed in a location suggested by an internal algorithm, aligned to existing nodes. Specifically, the placement algorithm used is similar to when pressing `TAB` with a node selected. For more details, see: https://www.pivotaltracker.com/story/show/181076066 # Important Notes - Visible visualizations enabled with the "eye icon" button are treated as part of a node. (In case of nodes with errors, visualizations are not visible, and are not treated as part of a node.)
2022-03-31 17:16:28 +03:00
- [Nodes created near existing nodes via the <kbd>TAB</kbd> key or by dropping a
connection are now repositioned and aligned to existing nodes.][3301] This is
to make the resulting graph prettier and avoid overlapping. In such cases,
created nodes will be placed below an existing node or on the bottom-left
diagonal if there is no space underneath.
Opening Component Browser by clicking on the output port (#3346) Double-clicking a node's output port or clicking the port with a right mouse button (RMB) creates a new node aligned to the clicked node. #### Visuals The screencast below demonstrates the following features: - double-clicking the left mouse button on a node's output port; - clicking the right mouse button on a node's output port; - alignment of the nodes created as a result of the actions described above; - corner case: double-clicking (and RMB-clicking) on output ports of a "collapsed" ("enterable") node; - double-clicking on a "collapsed" ("enterable") node still allows entering the node when done over an area of the node that is not the node's output port; - basic support for nodes with multiple output ports (shown on the `interface` demo scene). https://user-images.githubusercontent.com/273837/158991856-e0faa5f0-9d2f-44bd-bddd-ba314977db6e.mov The supplementary screencast below demonstrates that double-clicking or RMB-clicking a node's output port cancels the action of dragging a new connection from a node. https://user-images.githubusercontent.com/273837/158998097-100aed42-37ff-4467-939f-2b755ef0d3dc.mov https://www.pivotaltracker.com/story/show/181076145 # Important Notes - The "double-clicking a node" shortcut was previously used to allow entering a "collapsed" node (for example, a node created by pressing the `cmd+g` keyboard shortcut after selecting a group of nodes). This PR keeps that functionality when the user double-clicks on a node, as long as the mouse is not positioned over the node's output ports. - The support for nodes with multiple output ports is currently very basic. The information about a port (`Crumb`) is passed into the `create_node` function, but it is not passed further to `NodeSource`. The Node Searcher currently does not support passing port information through `NodeSource`.
2022-03-21 18:08:17 +03:00
- [Nodes can be added to the graph by double-clicking the output ports of
existing nodes (or by clicking them with the right mouse button).][3346]
Node searcher zoom & edited node growth/shrink animation (#3327) In this PR two things are implemented: 1. Node Searcher zoom factor (and therefore its size) is fixed no matter how you move the main camera. The node searcher is also positioned directly below currently edited node at all times. 2. Node growth/shrink animation when you start/finish node editing. After animation end the edited node zoom factor is also fixed and matches the zoom factor of the node searcher. See attached video with different ways of editing/creating nodes: https://user-images.githubusercontent.com/6566674/157348758-2880aa2b-494d-46e6-8eee-a22be84081ed.mp4 #### Technical details 1. Added several additional scene layers for separate rendering: `node_searcher`, `node_searcher_text`, `edited_node`, `edited_node_text`. Searcher is always rendered by `node_searcher` camera, edited node moves between its usual layers and `edited_node` layer. Because text rendering uses different API, all node components were modified to support change of the layer. 2. Also added `node_searcher` DOM layer, because documentation is implemented as a DOM object. 3. Added two FRP endpoints for `ensogl::Animation`: `on_end` and `set_value`. These endpoints are useful while implementing growth/shrink animation. 4. Added FRP endpoints for the `Camera2d`: `position` and `zoom` outputs. This allows to synchronize cameras easily using FRP networks. 5. Growth/shrink animation implemented in GraphEditor by blending two animations, similar to Node Snapping implementation. However, shrinking animation is a bit tricky to implement correctly, as we must always return node back to the `main` scene layer after editing is done.
2022-03-17 13:38:18 +03:00
- [Node Searcher preserves its zoom factor.][3327] The visible size of the node
searcher and edited node is now fixed. It simplifies node editing on
non-standard zoom levels.
Return creating node with (+) button & fix a regression (#3338) * Creating a new node with the (+) button (#3278) [The Task](https://www.pivotaltracker.com/story/show/180887253) A new (+) button on the left-bottom corner appeared. It may be clicked to open searcher in the middle of the scene, as an alternative to tab key. https://user-images.githubusercontent.com/3919101/154514279-7972ed6a-0203-47cb-9a09-82dba948cf2f.mp4 * The window_control_buttons::common was extracted to separate crate `ensogl-component-button` almost without change. * This includes a severe refactoring of adding nodes in general in the Graph Editor. The whole responsibility of adding new nodes (and starting their editing) was moved to Graph Editor - the Project View only reacts for GE events to show searcher properly. * The status bar was moved from the bottom-left corner to the middle-top of the scene. It does not collide with (+) button, and plays "notification" role anyway. * The `interface` debug scene was buggy. The problem was with one expression's span-tree. When I replaced it, the scene works. * I've removed "new searcher" API, as it is completely outdated. * I've changed code owners of integration tests to GUI team, as it is the team writing mostly the integration tests (int rust) * Fix regression #181528359 * Add docs & remove unused function * Fix & enable native Rust tests * Fix formatting Co-authored-by: Adam Obuchowicz <adam.obuchowicz@enso.org> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
2022-03-16 21:02:47 +03:00
- [Nodes can be added to the graph by clicking (+) button on the screen][3278].
The button is in the bottom-left corner. Node is added at the center or pushed
down if the center is already occupied by nodes.
Restrict Graph Editor Zoom (#3295) [Task link](#181181203). This is a reincarnation of PR [3273](https://github.com/enso-org/enso/pull/3273). The maximum zoom factor of Graph Editor is limited to 1.0x. It is not possible to zoom in from the default camera position. Debug Mode (activated with `ctrl-shift-d` shortcut) allows to zoom up to 100.0x (the previous behavior of Graph Editor). If you enable Debug Mode, then zoom in and disable Debug Mode - you won't see the immediate change of zoom factor back to 1.0x. But it will "jump" (with animation) back once you make a zoom in/out event with your controls. Video: https://user-images.githubusercontent.com/6566674/154037310-1d166737-353e-4ae6-aca1-f7840571ab16.mp4 # Important Notes This is a reincarnation of PR [3273](https://github.com/enso-org/enso/pull/3273). There are two changes since that PR: 1. Fixed bug with GeoMap zooming described [here](https://github.com/enso-org/enso/pull/3290). This is done by restricting `ZoomEvent` API so that it will never contain `amount` which is equal to `0.0`. 2. A few refactoring changes from https://github.com/enso-org/enso/pull/3289 to simplify code a bit.
2022-02-22 14:23:59 +03:00
- [Maximum zoom factor is limited to 1.0x if IDE is not in Debug Mode.][3273]
Debug Mode for Graph Editor (#3264)
2022-02-14 13:19:08 +03:00
- [Debug Mode for Graph Editor can be activated/deactivated using a
shortcut.][3264] It allows access to a set of restricted features. See
[debug-shortcuts].
Implement creating nodes by dropping a connection (#3231)
2022-01-26 14:23:55 +03:00
- [New nodes can be created by dragging and dropping a connection on the
scene.][3231]
- [Node connections can be dropped by pressing the Esc key while dragging
them.][3231]
Support source maps for JS-based visualizations (#3208)
2022-01-11 15:31:43 +03:00
- [Added support of source maps for JS-based visualizations.][3208]
Placement of newly opened Component Browser when nodes are selected (#3361) When a new node is created with the <kbd>TAB</kbd> key or by clicking the `(+)` on-screen button while multiple nodes are selected, place the new node below all the selected nodes. (Previously, the new node was placed below the node that was selected earliest.) Additionally, when placing a new node below an existing non-error node with a visualization enabled, place the new node below the visualization. (Previously, the new node was placed to the left of the visualization.) https://www.pivotaltracker.com/story/show/180887079 #### Visuals The following screencast demonstrates the feature on various arrangements of selected nodes, with visualization enabled and disabled. https://user-images.githubusercontent.com/273837/159971452-148aa4d7-c0f3-4b48-871a-a2783989f403.mov The following screencast demonstrates that new nodes created by double-clicking an output port of a node with visualization enabled are now placed below the visualization: https://user-images.githubusercontent.com/273837/160107733-e3f7d0f9-0161-49d1-8cbd-06e18c843a20.mov # Important Notes - Some refactorings that were needed for this PR were ported from the #3301 PR: - the code responsible for calculating the positions of new nodes was moved to a separate module (`new_node_position`); - the `free_place_finder` module was made a submodule of the `new_node_position` module, due to the latter being its only user.
2022-03-31 23:17:04 +03:00
- [Fixed the alignment of newly created nodes to existing nodes with
visualizations enabled.][3361] When applicable, new nodes are now placed below
visualizations. (Previously, they were placed to the left of the
visualizations.)
Colorful Histograms (#3153)
2021-11-18 17:17:38 +03:00
- [Fixed histograms coloring and added a color legend.][3153]
Lazy scatterplot for Vector & Table (#3655) First of all this PR demonstrates how to implement _lazy visualization_: - one needs to write/enhance Enso visualization libraries - this PR adds two optional parameters (`bounds` and `limit`) to `process_to_json_text` function. - the `process_to_json_text` can be tested by standard Enso test harness which this PR also does - then one has to modify JavaScript on the IDE side to construct `setPreprocessor` expression using the optional parameters The idea of _scatter plot lazy visualization_ is to limit the amount of points the IDE requests. Initially the limit is set to `limit=1024`. The `Scatter_Plot.enso` then processes the data and selects/generates the `limit` subset. Right now it includes `min`, `max` in both `x`, `y` axis plus randomly chosen points up to the `limit`. ![Zooming In](https://user-images.githubusercontent.com/26887752/185336126-f4fbd914-7fd8-4f0b-8377-178095401f46.png) The D3 visualization widget is capable of _zooming in_. When that happens the JavaScript widget composes new expression with `bounds` set to the newly visible area. By calling `setPreprocessor` the engine recomputes the visualization data, filters out any data outside of the `bounds` and selects another `limit` points from the new data. The IDE visualization then updates itself to display these more detailed data. Users can zoom-in to see the smallest detail where the number of points gets bellow `limit` or they can select _Fit all_ to see all the data without any `bounds`. # Important Notes Randomly selecting `limit` samples from the dataset may be misleading. Probably implementing _k-means clustering_ (where `k=limit`) would generate more representative approximation.
2022-08-23 15:12:22 +03:00
- [Lazy visualization for scatter plot.][3655]
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
- [Fixed broken node whose expression contains non-ASCII characters.][3166]
Register Views before creating them (#3181)
2021-12-08 10:11:58 +03:00
- [Fixed developer console warnings about views being created but not
registered.][3181]
Fix some edits not being sent to LangServ (#3186) Some edits were not being sent by IDE to Language Server, resulting in 3003 "Invalid version" errors being returned by LangServ, and forcing full invalidation (resynchronization) of text contents in LangServ. This change fixes such errors observed when opening a new project, creating a new project, or adding a new node to a project. Fixes #3094 ### Important Notes The root cause showed up to be actually two separate issues, both of them reproduced by an "opening a new project" scenario: 1. The automatic addition of `import Standard.Visualization` line, [done internally when opening a new project in `controller::Project::initialize()`](https://github.com/enso-org/enso/blob/c14a2d81698217349394597fea778fd86bba47df/app/gui/src/controller/project.rs#L137-L141), was not reaching the Language Server. The cause of it was a race condition with [`self.model.subscribe()` in `Module::runner()`](https://github.com/enso-org/enso/blob/c14a2d81698217349394597fea778fd86bba47df/app/gui/src/model/module/synchronized.rs#L268). In particular, the addition of the import was executed before the subscription, which resulted in an edition notification being lost and not sent to LangServer. The fix employed for this is to make the `subscribe()` call synchronous during the initialization of a project, instead of scheduling it for a non-deterministic later time. 2. There was [a bug in `synchronized::Module::edit_for_snipped()`](https://github.com/enso-org/enso/blob/7467efda592ab5d7ce29122af20020293f9ceacf/app/gui/src/model/module/synchronized.rs#L362), making it erroneously "optimize out" any code insertions detected by `TextEdit::from_prefix_postfix_differences()`. The fix employed for this was to improve the "optimizing out" condition, together with adding an accompanying test case verifying correct behavior (protecting against a future regression). Additionally, as a drive-by improvement, some statements in `ParsedSourceFile<>::serialize()` were reordered, to make them better match how the actual contents of an .enso file are structured, and thus make it easier to read/analyze the code.
2021-12-13 20:18:20 +03:00
- [Fixed developer console errors related to Language Server (mentioning code
3003 and "Invalid version"), occurring during project opening and after new
node cration.][3186]
Fix problems related to error visualisation evaluation (#3193) - Add parser & handler in IDE for `executionContext/visualisationEvaluationFailed` message from Engine (fixes a developer console error "Failed to decode a notification: unknown variant `executionContext/visualisationEvaluationFailed`"). The contents of the error message will now be properly deserialized and printed to Dev Console with appropriate details. - Fix a bug in an Enso code snippet used internally by the IDE for error visualizations preprocessing. The snippet was using not currently supported double-quote escaping in double-quote delimited strings. This lack of processing is actually a bug in the Engine, and it was reported to the Engine team, but changing the strings to single-quoted makes the snippet also more readable, so it sounds like a win anyway. - A test is also added to the Engine CI, verifying that the snippet compiles & works correctly, to protect against similar regressions in the future. Related: #2815
2021-12-21 12:00:57 +03:00
- [Fixed developer console error about failing to decode a notification
"executionContext/visualisationEvaluationFailed"][3193]
Component list panel integration (#3530) This PR contains all work for finishing integration of first Component List Panel in the IDE: * It adds a stub for the whole Component Browser View. The documentation panel is re-used from the old searcher. * It has the presenter implementation, integrating the view with Hierarchical Component List from the controller. * It extends the View API, so the integration is possible, making use of Component Group Set wrapper. * The selection integration was also merged into this PR, because it depended on the API extension mentioned above. However, we should avoid such practice in the future. https://user-images.githubusercontent.com/3919101/177816427-8c4285b4-8941-4048-a400-52f4acf77a9f.mp4 # Important Notes There are some known issues, to-be-fixed in the future. * The performance is bad. It should be improved with new text::Area, and the decent one shall come with [GridView inside component browser](https://www.pivotaltracker.com/story/show/182561072) * There is no keyboard navigation. It should also be delivered with [GridView](https://www.pivotaltracker.com/story/show/182561072). * The Favorites section is not [filtered out by node source type](https://www.pivotaltracker.com/story/show/182661634).
2022-07-14 15:00:52 +03:00
- [New Version of the Node Searcher - the Component Browser][3530] The available
methods, atoms and functions are presented in nice, categorized view. The most
Component Browser with Grid View (#3766) This PR introduced an overhauled Component List Panel implementation, making use of the efficient EnsoGL grid view component. Also, it delivers a couple of new features: * A part of the new design: there are no more section headers in grid, instead groups are "glued" together. The local scope section is under "popular" (old "favorites"). * The keyboard management inside grid works. * there is a mouse hover highlight * selecting the lowest entry in section when jumping with navigation bar. * accepting input as-is with cmd/ctrl + Enter. https://user-images.githubusercontent.com/3919101/194561890-fffb9b41-2f0d-4357-8d9a-5038a6bcb023.mp4 ### Important Notes **What is not implemented:** * [Focus management between panels.](https://www.pivotaltracker.com/story/show/180872763) The grid is always focused. To accept the current input, use ctrl+Enter shortcut. * [Proper handling of selection when having empty space on the right and pressing right arrow.](https://www.pivotaltracker.com/story/show/183487880) * When entering a module, its name is not added to the input as described in the design doc. Will be a part of [this User Story](https://www.pivotaltracker.com/story/show/181058321). **Known issues** * [the selection, especially in the local scope section, has sometimes an undesirable offset](https://www.pivotaltracker.com/story/show/183487730). The cause is known, but not so easy to fix. * The inserted nodes are often producing errors. The Browser's inherits the outdated understanding of the language from old Node Searcher, and it does not include new form of imports, static methods etc. Those all will be fixed as a part of [this User Story](https://www.pivotaltracker.com/story/show/181058321). * The performance is improved, but still not ideal, due to problems in [text areas](https://www.pivotaltracker.com/story/show/183406745). * To scroll the documentation panel, you must first click on it.
2022-10-14 13:42:59 +03:00
popular tools are available at hand. The panel is unstable, and can be
disabled with the `--enable-new-component-browser=false` flag.
Handling exceptions in IDE main to avoid entering "zombie process" state. (#3648) This is meant to address https://www.pivotaltracker.com/story/show/182691027.
2022-08-16 15:56:08 +03:00
- [Fixed error handling during startup.][3648] This prevents entering IDE into a
"zombie" state, where processes were started but not visible to user. They
could cause issues with starting further IDE instances.
IDE uses new visualization API (#3661)
2022-09-01 15:33:46 +03:00
- [New nodes are created in the project source when the searcher is opened and a
new node is created.][3645]
Improved Vector/Array interop (#3667) `Vector` type is now a builtin type. This requires a bunch of additional builtin methods for its creation: - Use `Vector.from_array` to convert any array-like structure into a `Vector` [by copy](https://github.com/enso-org/enso/pull/3667/commits/f628b28f5ffa0bcdceb64a7604317b2f7aee58bd) - Use (already existing) `Vector.from_polyglot_array` to convert any array-like structure into a `Vector` **without** copying - Use (already existing) `Vector.fill 1 item` to create a singleton `Vector` Additional, for pattern matching purposes, we had to implement a `VectorBranchNode`. Use following to match on `x` being an instance of `Vector` type: ``` import Standard.Base.Data.Vector size = case x of Vector.Vector -> x.length _ -> 0 ``` Finally, `VectorLiterals` pass that transforms `[1,2,3]` to (roughly) ``` a1 = 1 a2 = 2 a3 = 3 Vector (Array (a1,a2, a3)) ``` had to be modified to generate ``` a1 = 1 a2 = 2 a3 = 3 Vector.from_array (Array (a1, a2, a3)) ``` instead to accomodate to the API changes. As of 025acaa676d2d020ef368405531d3a3cf8ea73de all the known CI checks passes. Let's start the review. # Important Notes Matching in `case` statement is currently done via `Vector_Data`. Use: ``` case x of Vector.Vector_Data -> True ``` until a better alternative is found.
2022-09-13 06:07:17 +03:00
- [Proper Polyglot Vector and Array Support][3667]
IDE uses new visualization API (#3661)
2022-09-01 15:33:46 +03:00
- [IDE uses new visualization API.][3661]
Split long lines to 1024 long chunks (#3665) Avoid long lines when using `dom().set_inner_text` - rather split the long lines to 1024 chunks and insert them as individual `<div>` elements. # Important Notes I was testing the behavior on following program: ``` from Standard.Base import all import Standard.Base.Data.Statistics import Standard.Visualization main = number1 = 200000 operator1 = 0.up_to number1 . to_vector . map .noise operator2 = operator1.sort operator3 = operator2.to_text ``` before my change the visualization of `operator3` was blank. With my change it gets filled with data.
2022-08-29 11:02:33 +03:00
- [Visualization of long textual values improved][3665]
Show Visualisation Preview when Selecting Item on Searcher (#3691) Implements [#182634050](https://www.pivotaltracker.com/story/show/182634050). Enables visualization previews for selections in the searcher. Works for the old Searcher and the new Component Browser, but it was easier to show the examples for the old searcher, as the suggestions seem to be better/faster available currently (this will improve with the new implementation using better strings and the new GridView). https://user-images.githubusercontent.com/1428930/188898560-fc4f412a-1529-49f7-9958-28bf5e01c001.mp4 Aborting an edit now also correctly reverts a node. https://user-images.githubusercontent.com/1428930/188898549-ddd41294-2571-4e2e-b6d5-909cbf71de04.mp4
2022-09-16 19:05:40 +03:00
- [Selecting a suggestion from the searcher or component browser now updates the
visualisation of the edited node to preview the results of applying the
suggestion.][3691]
Remove here keyword (#3749) Changelog - Remove `HERE` keyword - Replace `here` with module name when generating code
2022-09-29 21:34:17 +03:00
- [Remove here keyword from IDE.][3749]
Update shortcuts to reflect Component Browser design docs. (#3823) When no node is edited, `Enter` creates a new one (opening Component Browser). The shortcut for entering node was changed to `cmd + Enter`
2022-10-25 20:21:12 +03:00
- [Shortcut changes:][3823] Pressing `Enter` when no node is edited opens
Component Browser. Entering node shortcut changed to `cmd` + `Enter`.
Scrollbar LMB click and hold scrolling (#3824)
2022-10-26 21:20:44 +03:00
- [Added support for scrolling by pressing and holding a mouse button on a
scrollbar.][3824]
add scroll overshoot bounce animation (#3836) Implements https://www.pivotaltracker.com/n/projects/2539304/stories/183390749 https://user-images.githubusercontent.com/919491/198984088-9c4f03db-922f-4503-83fa-f0301a11239e.mp4 # Important Notes - The overshoot bounce animation is implemented as a animation-like FRP mixin. It is currently defined using `define_endpoints` macro, but should be migrated to `define_endpoints_2` as soon as it supports "frp mixins" - definitions that extend external networks.
2022-11-07 13:50:47 +03:00
- [Added scroll bounce animation][3836] which activates when scrolling past the
end of scrollable content.
Implement Lazy Text Visualisation. (#3910) Implements [#183453466](https://www.pivotaltracker.com/story/show/183453466). https://user-images.githubusercontent.com/1428930/203870063-dd9c3941-ce79-4ce9-a772-a2014e900b20.mp4 # Important Notes * the best laziness is used for `Text` type, which makes use of its internal representation to send data * any type will first compute its default string representation and then send the content of that lazy to the IDE * special handling of files and their content will be implemented in the future * size of the displayed text can be updated dynamically based on best effort information: if the backend does not yet know the full width/height of the text, it can update the IDE at any time and this will be handled gracefully by updating the scrollbar position and sizes.
2023-01-24 23:55:36 +03:00
- [The default text visualisation now loads its content lazily from the
backend][3910]. This means that the visualisation cannot be overwhelmed by
large amounts of data.
Make a VCS save on ctrl+s shortcut (#3923) Save a snapshot of the project directory to the VCS on `ctrl+s`. If the operation fails because the VCS was not initialized previously, it will try to initialize the VCS first and then save a snapshot.
2022-12-02 15:39:11 +03:00
- [Added project snapshot saving on shortcut][3923]
Visual indication of outdated VCS snapshot (#3950) This PR provides a visual indication of whether the project's current state differs from the most recent snapshot saved in the VCS. The project name displayed in the IDE changes to a darker text to indicate that the VCS snapshot is outdated, and back to a lighter text when the current project state corresponds to the last saved VCS snapshot. https://user-images.githubusercontent.com/117099775/208088438-20dfc2aa-2a7d-47bf-bc12-3d3dff7a4974.mp4 The outdated project snapshot indicator is set when: * A node is moved. * A node is added or removed. * The text editor is used to edit the text. * The project is auto-saved, and the auto-saved project state does not correspond to the last saved snapshot in the VCS. The outdated project snapshot indicator is cleared when: * A new project snapshot is successfully saved using `ctrl+s`. * The project is auto-saved, and the auto-saved project state is confirmed to correspond to the last saved snapshot in the VCS. This occurs, for example, when a project change is undone and the project is reverted to the last saved snapshot state. The auto-save events do not occur immediately after a project change but have a short delay, thus the VCS status update is affected by the same delay when triggered by an auto-save event.
2022-12-20 00:22:33 +03:00
- [The color of the displayed project name indicates whether the project's
current state is saved in a snapshot.][3950] The project name is darker when
the project is changed from the last saved snapshot and lighter when the
snapshot matches the current project state.
Add a shortcut for interrupting the program (#3967) Add shortcuts for interrupting and restarting the program execution.
2022-12-12 20:48:42 +03:00
- [Added shortcut to interrupt the program][3967]
Basic dropdown widget integration (#4013) Implements https://www.pivotaltracker.com/n/projects/2539304/stories/184023445 Added a dropdown widget to graph node for all span tree nodes that have tag values present. When an option is selected, the controller receives a partial expression update, which targets specific crumbs of the expression (similar to how edge endpoint updates work). https://user-images.githubusercontent.com/919491/210219931-8ae418fd-3ac4-44a5-abea-9e670f15cdf9.mp4 # Important Notes Right now the dropdown widget is recreated every time the node is edited, including a dropdown option being selected. This causes it to close every time. I wanted to get around that by diffing span trees, but I wasn't able to do it in useful way. Additionally, current implementation of node input expression view heavily relies on being reinitialized from scratch every time. This led to more necessary changes than I was comfortable with for this task. I believe it will be easier to implement it as part of more complete widget support, especially after dynamic data support, as we will have proper widget type information.
2023-01-11 17:32:25 +03:00
- [Added suggestion dropdown for function arguments][4013]. The dropdown is
present only when the argument is of type that has a predefined set of values.
Separate component browser sections for every namespace libraries are imported from (#4044) This PR adds new sections to the component browser section navigator bar. The sections are based on the namespaces from which libraries are imported. Selecting a namespace section from the navigator bar highlights the modules from that namespace. Selecting a module from a different namespace switches the navigator bar indicator to the correct namespace category. The currently selected namespace is also shown as the root of the breadcrumbs. https://user-images.githubusercontent.com/117099775/212144719-2470a99d-8d8c-47ca-ab50-5bac65468090.mp4 For a new project where only the `Standard` namespace exists the only visible change is the breadcrumbs. Adding for example additional modules in the project `src` folder will create them in the `local` namespace, this namespace will show up as a separate navigator section.
2023-01-23 14:57:17 +03:00
- [Separate component browser navigator sections for modules imported from
different namespaces][4044]
Exclude components with a "PRIVATE" tag from the component browser (#4085) This PR removes components from the component browser if they contain a "PRIVATE" tag. Private components from the current module or project are not hidden. ![image](https://user-images.githubusercontent.com/117099775/214826165-9fe2cbee-1559-4602-80e0-5d3ce29d8cef.png)
2023-02-13 12:57:55 +03:00
- [Internal components (private API) are not displayed in the component
browser.][4085]
Ensure Table Visualisation is the Default Visualization for Tables (#4120) Adds a mechanism for the GUI to choose an appropriate default visualization for a newly created node. https://user-images.githubusercontent.com/1428930/216641714-2410d2c9-44d2-45f0-856d-1f995421c94b.mp4 # Important Notes This is a workaround for [missing functionality](https://www.pivotaltracker.com/story/show/184390437) that would take much longer to implement.
2023-02-08 02:23:24 +03:00
- [The correct default visualisation for tables is shown on new nodes.][4120]
Roll back last VCS snapshot (#4050) Fixes #5001 This PR implements reverting the current project state to the last state saved into the VCS. This action is performed on `ctrl+r`. https://user-images.githubusercontent.com/117099775/216645556-1bf34ee7-fdb4-4833-bcad-670d688a3199.mp4 # Important Notes * Currently on `vcs/restore` all expressions are invalidated and all nodes are re-executed. This is tracked in [task](https://www.pivotaltracker.com/n/projects/2539304/stories/184368950).
2023-02-16 21:14:34 +03:00
- [Added restoring of last project snapshot on shortcut.][4050]
Dynamic dropdown support (#4072) Implementation of https://www.pivotaltracker.com/story/show/184012743 https://user-images.githubusercontent.com/919491/214082311-cf49e43c-1d1f-4654-903c-a4224cd954d8.mp4 This is also a step towards more general widget support. The widget metadata is queried using `Meta.get_annotation` method through a dedicated visualization. For now only `Single_Choice` case is handled, and always all suggestions are is returned. # Important Notes There are limitations as to which node segments receive a widget. Only chain method calls are supported now (`thing.method` syntax), and only outside of lambda scope. Widgets in lambdas will require support for visualisations of lambda subexpressions, which is currently missing in the engine. The IDE technically tries to place the widgets there, but the data never arrives. It should work once the engine support is added. This PR includes a mock for `Meta.get_annotation` call that only supports `Table.at` method. Real implementation is a separate task that is already in progress.
2023-02-04 03:50:24 +03:00
- [Added contextual suggestions to argument dropdowns][4072]. Dropdowns will now
contain suggestions which are based on evaluated data.
Add a shortcut to toggle the visibility of private components in the component browser (#5582) Closes #4962 This PR adds the `cmd+alt+p` shortcut to toggle the visibility of components with a "PRIVATE" tag in the component browser. The default is to have these private components hidden. https://user-images.githubusercontent.com/117099775/219106357-0b14a5b5-404f-44dd-b30c-5389054683a7.mp4
2023-02-21 00:24:51 +03:00
- [Added a shortcut to show internal components (private API) in the component
browser.][5582]
Improve searching of component browser entries (#5645) Closes #5102 This PR improves searching entries in the component browser. Now the searcher input is also matched to the code that a component would generate, and the best match of the two is used for filtering and sorting the components in the component browser. https://user-images.githubusercontent.com/117099775/219328904-c7a067d5-4998-4ee5-8475-d4974cd7bff5.mp4 #### Entry name formatting Additionally, the component entry's displayed name format is changed to show the method's name first, followed by the type name in parentheses. This formatting fits better in the narrow columns of the component browser.
2023-02-17 02:21:37 +03:00
- [Improved component browser entry filtering and sorting][5645]. The component
browser will now provide suggestions matching either the component's label or
the corresponding code.
Support widgets and placeholders in more complex expressions (#5656) Implements https://github.com/enso-org/enso/issues/5032 Added support for widgets in infix expressions (right now only used for file paths) <img width="306" alt="image" src="https://user-images.githubusercontent.com/919491/218736181-98965cd4-2a8e-4f7a-bbf8-ab302ac5b22c.png"> Widgets and placeholders are handled for all chained methods within a node <img width="292" alt="image" src="https://user-images.githubusercontent.com/919491/218736249-a0190115-623e-4e66-aff4-90eb2a50685d.png"> The qualified method call convention and static methods no longer confuse the argument placeholders <img width="374" alt="image" src="https://user-images.githubusercontent.com/919491/218736628-24073f5c-0512-4b37-a271-0248bc954802.png"> Type constructor expressions now receive placeholder arguments. The placeholders work on nested expressions within a node. <img width="405" alt="image" src="https://user-images.githubusercontent.com/919491/218737379-b53ff125-3910-48f3-bb9f-a0e7b1684ab9.png">
2023-02-20 09:39:39 +03:00
- [Improved argument placeholder resolution in more complex expressions][5656].
It is now possible to drop node connections onto missing arguments of chained
and nested function calls.
Match component browser entries by alias (#5678) Closes #5340 This PR adds matching searched component browser entries by alias. Now the searcher input is also matched to the `ALIAS` tags of a component, and the best match is used for filtering and sorting the components in the component browser. The alias match scores are reduced by a factor to give them a lower priority when sorting filtered entries in the component browser. Multiple aliases for a single entry can be obtained from either multiple `ALIAS` tags in the documentation, or comma-separated aliases inside one `ALIAS` tag. When the searcher input matches one of the entry's aliases the entry in the component browser is displayed as `alias (label)`. https://user-images.githubusercontent.com/117099775/220571385-d6c2aba6-f13b-4517-9cdf-fe146eeb751a.mp4
2023-02-23 18:40:38 +03:00
- [The component browser suggestions take into account entry aliases][5678]. The
searcher input is now matched to entry aliases too. The alias match is used to
filter and sort component browser entries.
Use cached icons in Component Browser (#5779) Closes #5189 The component browser uses cached icons, both on the cached list and the navigator panel. It reduced the number of draw calls by 18.
2023-03-02 17:51:42 +03:00
- [The Component Browser icons are cached on texture][5779] improving its
performance on slower machines.
Fix missing visualization preview in CB (#5757) Closes #5639 This PR fixes a regression introduced in #4120, due to which new nodes that were being edited had an empty visualization preview. Now newly created visualization containers do get a default visualization set even before the visualization's input type is set. https://user-images.githubusercontent.com/117099775/221256294-c87a50da-c8b0-4f00-bf84-f5ae551fca72.mp4
2023-02-27 23:10:23 +03:00
- [Fixed missing result preview when editing nodes.][5757]
Retry IDE controller initialization. (#5802) This mainly fixes #5627 in both scenarios: when the initProtocol method takes too long time and also when we run GUI before LS listens for new connections. If the IDE initialization fails (e.g. due to above two reasons), it is retried 3 times, waiting some time.
2023-03-07 18:49:40 +03:00
- [Application retries its initialization after failures][5802], allowing a
reconnecting after connectivity problems.
Better sorting after filtering items in the Component Browser (#4115) Fixes #5849 Now, the filtering alters the groups' layout, so the group with the best match are placed first. Also, we ensure that the best match is selected after filter change. ![image](https://user-images.githubusercontent.com/3919101/224324736-0b4cdfb1-edb2-4d12-aab0-7cfb36207230.png) # Important Notes After all, I haven't taken the advices from [the task description](#5849): they turned out to require very difficult refactoring.
2023-03-16 14:23:40 +03:00
- [Improved Component Browser Filtering][4115]. The best match is always
selected first, and the groups are rearranged, so the best matches are on the
bottom.
Named arguments support in IDE (#5774) Added support for named arguments in IDE. https://user-images.githubusercontent.com/919491/223681303-4c716639-d06e-4e33-aa22-6ebca2801b01.mp4 Named arguments are now recognized in node expressions. The function argument placeholders are rendered around series of named arguments. Insertion and deletion of arguments either by connection dragging or by widget selection will cause arguments around to be rewritten into appropriate form, such that the meaning of the expression doesn't change. We no longer need to introduce any wildcards (`_`) in argument positions when editing an argument list of a resolved method. ![image](https://user-images.githubusercontent.com/919491/223682460-143eb6d7-5ac9-4732-9520-71216cbbe58f.png) For unresolved function calls, the old behaviour remains, as we don't have data about argument names or their desired order.
2023-03-10 00:23:25 +03:00
- [Named arguments syntax is now recognized in IDE][5774]. Connections to
function arguments will now use named argument syntax instead of inserting
wildcards on all preceding arguments.
Cognito auth 2/7 - add authorization app (#5798) 2nd PR for IDE/Cloud authorization with cognito. This PR introduces boilerplate react app + some amplify code to fetch the access token + username of the currently logged in user, if they are already authenticated. Registration + Login + Set Username + Forgot Password flows are to be added in next PRs to keep the changes reviewable.
2023-03-15 14:54:16 +03:00
- [Added boilerplate React app for authorization via Cognito+AWS Amplify][5798].
This PR adds a React app that renders the dashboard (which has been ported
from the cloud. The dashboard displays a list of projects, and allows users to
open them in the IDE (which is not part of the React app, but can be switched
to from the dashboard). The PR also adds authentication+authorization (i.e.,
sign up and sign in for users), via either email/password or GitHub/Google.
New documentation parser (#5917) Implement new Enso documentation parser; remove old Scala Enso parser. Performance: Total time parsing documentation is now ~2ms. # Important Notes - Doc parsing is now done only in the frontend. - Some engine tests had never been switched to the new parser. We should investigate tests that don't pass after the switch: #5894. - The option to run the old searcher has been removed, as it is obsolete and was already broken before this (see #5909). - Some interfaces used only by the old searcher have been removed.
2023-03-15 18:43:51 +03:00
- [New Enso documentation parser][5917]. Smaller and faster; enables planned
improvements to internal documentation representation.
support custom widget entry labels (#5705) Implements #5640 and #5650 It made sense for me to implement those two together, as I wanted to make sure that the necessary widget API changes will support custom entry values for both dynamic and static data. - Added support for custom dropdown labels defined on the method annotations - Added shortening of static dropdown values, which resolves | dynamic dropdown - custom labels | static dropdown - automatic shortening | |-|-| |![image](https://user-images.githubusercontent.com/919491/220117241-8682736e-d750-4eeb-b9bb-cd6cfce42356.png)|![image](https://user-images.githubusercontent.com/919491/220117412-05ad7f4a-3ccf-468b-a976-c52395a497e2.png)| # Important Notes During implementation I had multiple data update order issues caused by FRP network forming a diamond shape. Two inputs that are often updated together were combined with `all` combinator, and that was further fed into the dropdown. This caused two updates to propagate through the whole network, and one of them was immediately outdated. To fix this and similar future scenarios, I've added an `next_tick` FRP node. It buffers the incoming events until the next browser microtask, preserving only the last received event. Currently if it is called inside a `requestAnimationFrame` callback, the effects of that processing will only be rendered in the next frame. Later this can be mitigated by delaying the rendering logic until the microtask queue is empty.
2023-03-17 13:06:32 +03:00
- [Dropdown widgets now support custom labels][5705] and automatically generate
shortened labels for entries with long module paths. When an option is
selected from the dropdown, the necessary module imports are inserted,
eliminating the need for fully qualified names.
A drop-down that allows changing the execution mode. (#6130) Implements https://github.com/enso-org/enso/issues/5931. https://user-images.githubusercontent.com/1428930/228532453-2032b376-1aa5-4140-8331-be37e4e675d4.mp4 # Important Notes Not functional yet, as it needs integration with the engine.
2023-04-18 13:26:17 +03:00
- [The IDE now has a new UI element for selecting the execution mode of the
project][6130].
Add tooltips to the action bar (#6035) Implements #5933: adding tooltips to the buttons next to nodes. To make the UI consistent, I've added tooltips to the `ToggleButton` class directly, since whenever you have an icon button, it seems helpful to have a tooltip. `ToggleButton` is only used for the profiling button in the top-right corner and the buttons next to nodes. The output context switch button [isn't implemented yet](https://github.com/enso-org/enso/issues/5929), but once it is, adding a tooltip should be one-liner. ![Recording 2023-03-22 at 17 21 58](https://user-images.githubusercontent.com/607786/226972920-81033b37-001f-49eb-9fc6-453120f01760.gif)
2023-03-27 20:02:06 +03:00
- [Added tooltips to icon buttons][6035] for improved usability. Users can now
quickly understand each button's function.
Project Sharing (#6077) Enso will now associate with two file extensions: * `.enso` — Enso source file. * If the source file belongs to a project under the Project Manager-managed directory, it will be opened. * If the source file belongs to a project located elsewhere, it will be imported into the PM-managed directory and opened; * Otherwise, opening the `.enseo` file will fail. (e.g., loose source file without any project) * `.enso-project` — Enso project bundle, i.e., `tar.gz` archive containing a compressed Enso project directory. * it will be imported under the PM-managed directory; a unique directory name shall be generated if needed. ### Important Notes On Windows, the NSIS installer is expected to handle the file associations. On macOS, the file associations are expected to be set up after the first time Enso is started, On Linux, the file associations are not supported yet.
2023-04-06 16:26:37 +03:00
- [File associations are created on Windows and macOS][6077]. This allows
opening Enso files by double-clicking them in the file explorer.
AI Completions (#5910)
2023-06-19 00:54:06 +03:00
- [AI-powered code completions][5910]. It is now possible to get AI-powered
completions when using node searcher with Tables.
Widgets integrated with graph nodes (#6347) Rewrites node input component. Now the input is composed of multiple widget components arranged in a tree of views with automatic layout. That allows creating complex UI elements on top of the node itself, and further widget positions will be automatically adapted to that. The tree roughly follow the span tree, as it is built by consuming its nodes and eagerly creating widgets from them. The tree is rebuilt every time the expression changes, but that rebuild process reuses as much previously created widgets as possible, and only updates their configuration as needed. Each widget type can have its own configuration options that can be passed to it from the parent, or assigned based on configuration received from the language server. <img width="773" alt="image" src="https://user-images.githubusercontent.com/919491/233439310-9c39ea88-19bc-43da-9baf-1bb176e2724e.png"> # Important Notes For now, all span-tree updates are sent over to the shared Frp endpoint of the whole tree, so there is no mechanism for intercepting them by the parent widgets. One idea would be to use existing bubbling/capturing events on widget display objects for that purpose, but I think existing implementation is simpler and more convenient, and we can always easily change that if we have a use for it. There are some issues with performance due to much more display objects being created on the graph. Expect it to be a little worse, especially at initialization time.
2023-04-26 22:37:54 +03:00
- [Added capability to create node widgets with complex UI][6347]. Node widgets
such as dropdown can now be placed in the node and affect the code text flow.
Ability to change the execution environment between design and live. (#6341) Integrate the UI for electing the Execution Environment with the Language Server and unify existing uses. Implements #5930 + actual integration instead of just mocking it. https://user-images.githubusercontent.com/1428930/232919438-6e1e295a-34fe-4756-86a4-5f5d8f718fa0.mp4 # Important Notes The console output is only emitted as part of the `INFO` level. A better check would be to look at the messages sent to the backend in the developer console.
2023-04-25 23:28:15 +03:00
- [The IDE UI element for selecting the execution mode of the project is now
Disregard visualisation for selection of nodes. (#6487)
2023-05-04 21:43:08 +03:00
sending messages to the backend.][6341].
Show error pop-up when failing to rename a project (#6366) Closes #5065: when a project can't be renamed, it now shows an error pop-up and stays in edit mode. https://user-images.githubusercontent.com/607786/234025360-6761f7d6-c13c-479c-a0ba-8af5d81f6e87.mp4
2023-05-08 13:12:26 +03:00
- [Feedback when renaming a project][6366]. When the user tries to rename the
project to an invalid name, a helpful error message is shown and the text
field stays the same as to give the user the opportunity to fix the mistake.
Run prettier on `CHANGELOG.md`; bump prettier (#6571)
2023-05-05 07:52:22 +03:00
- [Area selectionof nodes no longer takes into account the visualisation that
Disregard visualisation for selection of nodes. (#6487)
2023-05-04 21:43:08 +03:00
belongs to the node.][6487].
Finishing Vector Editor (#6470)
2023-05-02 12:24:20 +03:00
- [List Editor Widget][6470]. Now you can edit lists by clicking buttons on
nodes or by dragging the elements.
Implement loading spinner for visualisations. (#6512) Fixes #5088. Adds a ensoGL spinner for visualizations waiting on data. https://user-images.githubusercontent.com/1428930/236801655-67a0ffed-da5d-4e27-8797-cd8126cb86d9.mp4 # Important Notes This spinner will not show up for the duration where visualizations are processing data on the frontend. If this is a concern, visualization need to implement heir own loading spinner, or we need to provide a unified API for them to keep the spinner visible.
2023-05-12 07:41:55 +03:00
- [Visualisations now show a loading spinner while waiting on data.][6512].
Fix cut-off in text visualisations (#6421) Closes #6196. Three things were going wrong: - Not directly contributing, but adding confusion was the fact that padding of 5px was added in two different places. Since the 10px we've had up until now looked better, especially given the size of the rounded corners, I've kept it at 10px, but only applied in one place. - The main issue was that the length the scrollbars scroll over didn't take padding into account. At the same time, I changed the `max` and `thumb_size` variables to the coordinate system of the content. This is also how they're being used in `ScrollArea`, which is the only other place where `Scrollbar`s are being used. - The line height of text grid entries was set to the default of 1.2. That's the default line height in browsers, which is great for multi-line text and elements whose height is greater than the line height. In this case, however, where the height and the font size are set to the same value, the default setting of 1.2 pushes the text below the allotted space. https://user-images.githubusercontent.com/607786/234297411-8c0b3851-5977-4ca5-b3b4-5b0782510e14.mp4
2023-05-04 11:11:18 +03:00
- [Fixed text visualisations which were being cut off at the last line.][6421]
Fix #5075: stop panning on full-screen visualisation (#6530) Closes #5075: dragging or scrolling while a visualisation is in full screen caused the camera to move in the graph editor. The problem was that clicking on the visualisation triggered some FRP node that indicated that the project list should be closed, which then indicated that the navigator shouldn't be disabled. However, the FRP code in the graph editor interpreted "shouldn't be disabled" as "should be enabled", ignoring the fact that there's also a full-screen visualisation, which should always disable the navigator. https://user-images.githubusercontent.com/607786/235908932-0b579d69-5fd8-438e-a82b-02678d8e6156.mp4
2023-05-05 12:04:07 +03:00
- [Fixed a bug where, when scrolling or dragging on a full-screen visualization,
the view of the graph changed as well.][6530]
Fix #6377: Change ctrl-r shortcut (#6620) Fixes #6377: The fact that `ctrl-r` was restoring the project to potentially the initial state was confusing. This PR changes that shortcut to `ctrl-shift-r`, as discussed in #6377. Note that: - `ctrl-shift-r` was already taken by the re-execution shortcut, so that got the `ctrl-alt` modifiers instead, along with the interruption shortcut for consistency. - `ctrl-alt-shift-r` was already taken by a shortcut to refresh the whole Electron app, so that wasn't available.
2023-05-10 11:40:24 +03:00
- [Changed the shortcut for restoring to the last saved version of a project
from <kbd>cmd</kbd>+<kbd>r</kbd> to
<kbd>cmd</kbd>+<kbd>shift</kbd>+<kbd>r</kbd>][6620] to make it less likely
that it would be triggered by accident. As a consequence, the program
execution shortcuts changed from
<kbd>cmd</kbd>+<kbd>shift</kbd>+<kbd>t</kbd>/<kbd>r</kbd> to
<kbd>cmd</kbd>+<kbd>alt</kbd>+<kbd>t</kbd>/<kbd>r</kbd>.
Fix #6287: wrong nested breadcrumb ordering (#6617) Fixes #6287. When selecting a nested breadcrumb, a race condition would happen: all new breadcrumbs were being added in a separately spawned task whose execution was thus indeterministic. https://github.com/enso-org/enso/assets/607786/73734805-292d-42ce-b08a-060a987d99bb
2023-05-11 17:59:19 +03:00
- [Fixed a bug where selecting a nested breadcrumb would cause the order of
breadcrumbs to change incorrectly.][6617]
Change full-screen visualisation shortcut to shift-space (#6663) Fixes #6260: The shortcut to open the full-screen visualisation is now `shift-space` so it doesn't interfere with the `space` shortcut to toggle the mini-visualisation.
2023-05-17 12:07:47 +03:00
- [Changed the shortcut to show the full-screen visualization for a node from
<kbd>space</kbd> <kbd>space</kbd> to <kbd>shift</kbd>+<kbd>space</kbd>.][6663]
so that it doesn't interfere with the shortcut for toggling the small
visualization.
Add cloud dashboard to changelog (#6688)
2023-05-18 00:20:49 +03:00
- [Cloud dashboard, which supersedes the startup screen][6279]. Features also
added in various other PRs. The new dashboard includes tables for projects,
folders, files and secrets, a list of templates from which new projects can be
created, a user menu, and a search bar.
Reloading file in LS after desynchronization. (#6752) Fixes #5203 This PR changes behavior when `text/applyChange` returned error. Before we always assumed that the change was _not_ applied, and tried to send full synchronization still assuming old file content. But this was not the case on some errors (timeouts for example). Now we instead reopen the file (getting its actual content) and then make a full invalidation. Also added a shortcut allowing manual file reloading, what may be useful in some kinds of error (and also allowed me testing of reopening file in the application). # Important Notes The unit tests of sending text updates were improved: now we actually check if all expected messages are emitted from the IDE.
2023-05-23 11:19:27 +03:00
- [The Application will try to reload file in backend on synchronization
failure][6752]. It should make it more resilient to connectivity issues and
occasional bugs. The reload may be forced by the user with
<kbd>cmd</kbd>+<kbd>shift</kbd>+<kbd>x</kbd> shortcut.
Fix #6521: Main module function calls shouldn't use project namespace (#6719) Fixes #6521: Picking a function from the CB that's defined in the main module now resolves to `Main.<func-name>` instead of `<project-name>.<func-name>`. Note that, when collapsing nodes to a function, this referral style was already used, so this is just a change in the behaviour of the CB.
2023-05-22 17:50:25 +03:00
- [When selecting a function from the main module through the component browser,
it is now referenced via the `Main` namespace instead of the project
namespace,][6719] e.g. `Main.func1` instead of `MyProject.func1`. This makes
it robust against project name changes.
Add dashboard button (#6474) Closes #6399: Adding a button to the top bar in the project view to return to the dashboard. Note that this just fires a DOM event (see #6399). To test it, you can add an event listener: `document.addEventListener('show-dashboard', console.log)` https://user-images.githubusercontent.com/607786/235687669-ab04339f-0f07-439a-9cd3-59d96815edaa.mp4
2023-05-23 17:23:23 +03:00
- [Added a button to return from an opened project back to the project
dashboard.][6474]
Stop graph editing when in full-screen visualization mode (#6844) Fixes #6754. The issue mentions being able to create and delete nodes when the full-screen visualisation is active. Besides those, you now also can't: - collapse nodes into a function - enter a function - exit a function
2023-05-26 16:08:16 +03:00
- [Keyboard shortcuts for graph editing are now disabled when the full-screen
visualization is active.][6844]
Show spinner when opening/creating a project, take #2 (#6827) * Remove unused code: project management in component browser * Encapsulate internal FRP logic of project list * Collapse some code paths * Open project passed on command line through presenter A project name or ID that is passed on the command line was initialised in the controller setup, before the presenters and views are set up. Now, we fully initialise the IDE before opening a project so we have control over the view while a project is being opened. * Show a spinner in all cases of opening a project * Let root presenter open/close projects when switching projects * Change spinner to make progress over a fixed period * Resolve issues when Project Manager API isn't available * Bump wasm size limit
2023-05-26 19:20:07 +03:00
- [A loading animation is now shown when opening and creating projects][6827],
as the previous behaviour of showing a blank screen while the project was
being loaded was potentially confusing to users.
Display error message in status bar when execution failed (#6918) Closes #6859 https://github.com/enso-org/enso/assets/6566674/326b4fd9-b26c-4252-aab6-3c205457a2fa Latest state: <img width="1369" alt="Screenshot 2023-06-02 at 12 34 23" src="https://github.com/enso-org/enso/assets/6566674/baf20d92-4b27-40c2-bd46-b71ea5b952fd"> # Important Notes - ~~Is current message to the user correct? Do we need to say something more?~~
2023-06-09 16:22:23 +03:00
- [Error message is displayed in the status bar when the backend reports
execution failed][6918].
Split CB documentation to smaller pages (#6893) Now documentation for types, constructors and methods is displayed separately, with a links between pages. It drastically improves the speed of documentation panel update (50-100x on my machine), and also provides more readable documentation. https://github.com/enso-org/enso/assets/6566674/05c77560-162b-4396-bfa0-1e79eb6dcc5f Before: <img width="620" alt="Screenshot 2023-05-31 at 01 02 47" src="https://github.com/enso-org/enso/assets/6566674/045ad3fc-470b-44d6-b453-e63c06711d06"> After: <img width="800" alt="Screenshot 2023-05-31 at 00 54 53" src="https://github.com/enso-org/enso/assets/6566674/cb76e757-66fa-4544-8ef9-80b0a54efe0b">
2023-06-02 10:14:50 +03:00
- [Performance and readability of documentation panel was improved][6893]. The
documentation is now split into separate pages, which are much smaller.
Fix redundant imports when selecting options from the dropdown widget (#7028) Fixes #6816. The code for adding imports for dropdown widgets was unified with CB. The code was moved from the searcher controller to the graph controller. Also, I changed the signature for a few `lookup_*` methods of the suggestion database, because I have always found it weird that they return `Option` instead of `Result`. They now work nicely with the surrounding code. https://github.com/enso-org/enso/assets/6566674/49125f8d-096e-4cca-a922-4811ed717a4d
2023-06-21 15:00:15 +03:00
- [IDE no longer inserts redundant imports when selecting options from dropdown
widgets][7028]. The code was unified with the component browser, and it now
correctly handles reexports and already existing imports.
Fix issues with mouse cursor position when editing nodes (#7014)
2023-06-19 16:54:47 +03:00
- [Fixed cursor position when ctrl-clicking the node][7014]. Sometimes
ctrl-clicking to edit the node placed the mouse cursor in the wrong position
in the text. This is fixed now.
Fix cut-off in text visualisations (#6421) Closes #6196. Three things were going wrong: - Not directly contributing, but adding confusion was the fact that padding of 5px was added in two different places. Since the 10px we've had up until now looked better, especially given the size of the rounded corners, I've kept it at 10px, but only applied in one place. - The main issue was that the length the scrollbars scroll over didn't take padding into account. At the same time, I changed the `max` and `thumb_size` variables to the coordinate system of the content. This is also how they're being used in `ScrollArea`, which is the only other place where `Scrollbar`s are being used. - The line height of text grid entries was set to the default of 1.2. That's the default line height in browsers, which is great for multi-line text and elements whose height is greater than the line height. In this case, however, where the height and the font size are set to the same value, the default setting of 1.2 pushes the text below the allotted space. https://user-images.githubusercontent.com/607786/234297411-8c0b3851-5977-4ca5-b3b4-5b0782510e14.mp4
2023-05-04 11:11:18 +03:00
AI Completions (#5910)
2023-06-19 00:54:06 +03:00
[5910]: https://github.com/enso-org/enso/pull/5910
Add cloud dashboard to changelog (#6688)
2023-05-18 00:20:49 +03:00
[6279]: https://github.com/enso-org/enso/pull/6279
Fix cut-off in text visualisations (#6421) Closes #6196. Three things were going wrong: - Not directly contributing, but adding confusion was the fact that padding of 5px was added in two different places. Since the 10px we've had up until now looked better, especially given the size of the rounded corners, I've kept it at 10px, but only applied in one place. - The main issue was that the length the scrollbars scroll over didn't take padding into account. At the same time, I changed the `max` and `thumb_size` variables to the coordinate system of the content. This is also how they're being used in `ScrollArea`, which is the only other place where `Scrollbar`s are being used. - The line height of text grid entries was set to the default of 1.2. That's the default line height in browsers, which is great for multi-line text and elements whose height is greater than the line height. In this case, however, where the height and the font size are set to the same value, the default setting of 1.2 pushes the text below the allotted space. https://user-images.githubusercontent.com/607786/234297411-8c0b3851-5977-4ca5-b3b4-5b0782510e14.mp4
2023-05-04 11:11:18 +03:00
[6421]: https://github.com/enso-org/enso/pull/6421
Fix #5075: stop panning on full-screen visualisation (#6530) Closes #5075: dragging or scrolling while a visualisation is in full screen caused the camera to move in the graph editor. The problem was that clicking on the visualisation triggered some FRP node that indicated that the project list should be closed, which then indicated that the navigator shouldn't be disabled. However, the FRP code in the graph editor interpreted "shouldn't be disabled" as "should be enabled", ignoring the fact that there's also a full-screen visualisation, which should always disable the navigator. https://user-images.githubusercontent.com/607786/235908932-0b579d69-5fd8-438e-a82b-02678d8e6156.mp4
2023-05-05 12:04:07 +03:00
[6530]: https://github.com/enso-org/enso/pull/6530
Fix #6287: wrong nested breadcrumb ordering (#6617) Fixes #6287. When selecting a nested breadcrumb, a race condition would happen: all new breadcrumbs were being added in a separately spawned task whose execution was thus indeterministic. https://github.com/enso-org/enso/assets/607786/73734805-292d-42ce-b08a-060a987d99bb
2023-05-11 17:59:19 +03:00
[6617]: https://github.com/enso-org/enso/pull/6617
Add cloud dashboard to changelog (#6688)
2023-05-18 00:20:49 +03:00
[6620]: https://github.com/enso-org/enso/pull/6620
Change full-screen visualisation shortcut to shift-space (#6663) Fixes #6260: The shortcut to open the full-screen visualisation is now `shift-space` so it doesn't interfere with the `space` shortcut to toggle the mini-visualisation.
2023-05-17 12:07:47 +03:00
[6663]: https://github.com/enso-org/enso/pull/6663
Reloading file in LS after desynchronization. (#6752) Fixes #5203 This PR changes behavior when `text/applyChange` returned error. Before we always assumed that the change was _not_ applied, and tried to send full synchronization still assuming old file content. But this was not the case on some errors (timeouts for example). Now we instead reopen the file (getting its actual content) and then make a full invalidation. Also added a shortcut allowing manual file reloading, what may be useful in some kinds of error (and also allowed me testing of reopening file in the application). # Important Notes The unit tests of sending text updates were improved: now we actually check if all expected messages are emitted from the IDE.
2023-05-23 11:19:27 +03:00
[6752]: https://github.com/enso-org/enso/pull/6752
Fix #6521: Main module function calls shouldn't use project namespace (#6719) Fixes #6521: Picking a function from the CB that's defined in the main module now resolves to `Main.<func-name>` instead of `<project-name>.<func-name>`. Note that, when collapsing nodes to a function, this referral style was already used, so this is just a change in the behaviour of the CB.
2023-05-22 17:50:25 +03:00
[6719]: https://github.com/enso-org/enso/pull/6719
Add dashboard button (#6474) Closes #6399: Adding a button to the top bar in the project view to return to the dashboard. Note that this just fires a DOM event (see #6399). To test it, you can add an event listener: `document.addEventListener('show-dashboard', console.log)` https://user-images.githubusercontent.com/607786/235687669-ab04339f-0f07-439a-9cd3-59d96815edaa.mp4
2023-05-23 17:23:23 +03:00
[6474]: https://github.com/enso-org/enso/pull/6474
Stop graph editing when in full-screen visualization mode (#6844) Fixes #6754. The issue mentions being able to create and delete nodes when the full-screen visualisation is active. Besides those, you now also can't: - collapse nodes into a function - enter a function - exit a function
2023-05-26 16:08:16 +03:00
[6844]: https://github.com/enso-org/enso/pull/6844
Show spinner when opening/creating a project, take #2 (#6827) * Remove unused code: project management in component browser * Encapsulate internal FRP logic of project list * Collapse some code paths * Open project passed on command line through presenter A project name or ID that is passed on the command line was initialised in the controller setup, before the presenters and views are set up. Now, we fully initialise the IDE before opening a project so we have control over the view while a project is being opened. * Show a spinner in all cases of opening a project * Let root presenter open/close projects when switching projects * Change spinner to make progress over a fixed period * Resolve issues when Project Manager API isn't available * Bump wasm size limit
2023-05-26 19:20:07 +03:00
[6827]: https://github.com/enso-org/enso/pull/6827
Display error message in status bar when execution failed (#6918) Closes #6859 https://github.com/enso-org/enso/assets/6566674/326b4fd9-b26c-4252-aab6-3c205457a2fa Latest state: <img width="1369" alt="Screenshot 2023-06-02 at 12 34 23" src="https://github.com/enso-org/enso/assets/6566674/baf20d92-4b27-40c2-bd46-b71ea5b952fd"> # Important Notes - ~~Is current message to the user correct? Do we need to say something more?~~
2023-06-09 16:22:23 +03:00
[6918]: https://github.com/enso-org/enso/pull/6918
Split CB documentation to smaller pages (#6893) Now documentation for types, constructors and methods is displayed separately, with a links between pages. It drastically improves the speed of documentation panel update (50-100x on my machine), and also provides more readable documentation. https://github.com/enso-org/enso/assets/6566674/05c77560-162b-4396-bfa0-1e79eb6dcc5f Before: <img width="620" alt="Screenshot 2023-05-31 at 01 02 47" src="https://github.com/enso-org/enso/assets/6566674/045ad3fc-470b-44d6-b453-e63c06711d06"> After: <img width="800" alt="Screenshot 2023-05-31 at 00 54 53" src="https://github.com/enso-org/enso/assets/6566674/cb76e757-66fa-4544-8ef9-80b0a54efe0b">
2023-06-02 10:14:50 +03:00
[6893]: https://github.com/enso-org/enso/pull/6893
Fix redundant imports when selecting options from the dropdown widget (#7028) Fixes #6816. The code for adding imports for dropdown widgets was unified with CB. The code was moved from the searcher controller to the graph controller. Also, I changed the signature for a few `lookup_*` methods of the suggestion database, because I have always found it weird that they return `Option` instead of `Result`. They now work nicely with the surrounding code. https://github.com/enso-org/enso/assets/6566674/49125f8d-096e-4cca-a922-4811ed717a4d
2023-06-21 15:00:15 +03:00
[7028]: https://github.com/enso-org/enso/pull/7028
Fix issues with mouse cursor position when editing nodes (#7014)
2023-06-19 16:54:47 +03:00
[7014]: https://github.com/enso-org/enso/pull/7014
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
SDF-based mechanism for making letters bold (#3385) Fixes [181641027](https://www.pivotaltracker.com/story/show/181641027). There are new methods of text::Area for making some letters bolder, without moving them nor any other letters in the line. Tested on DejaVuSans text: ![image](https://user-images.githubusercontent.com/3919101/162199723-524f7560-535f-4c98-bcb4-6b760ad8cb04.png) ![image](https://user-images.githubusercontent.com/3919101/162199806-e6582c56-3071-4653-8ad2-114df86cd6b7.png) ![image](https://user-images.githubusercontent.com/3919101/162199880-1836e902-8663-4696-bcb7-2b15c3c243c6.png) On MacOS: <img width="824" alt="Screenshot 2022-04-07 at 14 54 40" src="https://user-images.githubusercontent.com/3919101/162203730-ffda3096-7aab-443f-a45a-bfa18784ba36.png"> <img width="379" alt="Screenshot 2022-04-07 at 14 54 52" src="https://user-images.githubusercontent.com/3919101/162203751-f5ca2e26-fdb6-4521-9821-999111b80ac0.png"> <img width="160" alt="Screenshot 2022-04-07 at 14 54 58" src="https://user-images.githubusercontent.com/3919101/162203769-3c367f81-67bb-48aa-994c-42eeb131017e.png">
2022-04-12 20:39:08 +03:00
#### EnsoGL (rendering engine)
- [You can change font and set letters bold in the <code>text::Area</code>
component][3385]. Use the <code>set_font</code> and
<code>set_bold_bytes</code> respectively.
Fix depth-ordering update (#3486) There are two dirty flags in layers: depth_order_dirty and element_depth_order_dirty - one marking changed in Layer, second marking change in one of sublayers. The depth_order_dirty has a proper callback for setting element_depth_order_dirty of its parent. However, the latter did not propagate up. I fixed it by adding callback for element_depth_order_dirty which sets the depth_order_dirty of the parent. # Important Notes * The question to @wdanilo : is it possible, that I can propagate dirty directly to element_depth_order_dirty, without setting depth_order_dirty? As far as I understand the code, it would also work (and we would omit some unnecessary updates). * I tried to leave some logs, but I don't feel how to do that: the tooling I used was very specific, only the concrete ids of symbols and layers were logged, and I don't know how to generalize it.
2022-05-30 13:32:43 +03:00
- [Fixed a text rendering issue in nested sublayer][3486].
Grid View with Scrolling (#3588) **Note**: This PR also contains content of previous Grid View PR. We decided to discard the previous, because this one did some refactoring of old one, and it's not a big addition. Added a scrollable::GridView component, which just embeds the GridView in ScrollArea. Also, re-worked the idea of text layers. https://user-images.githubusercontent.com/3919101/179020359-512ee127-c333-4f86-bff5-f1cb4154e03c.mp4
2022-07-19 11:39:23 +03:00
- [Added a new component: Grid View.][3588] It's parametrized by Entry object,
display them arranged in a Grid. It does not instantiate all entries, only
those visible, and re-use created entries during scrolling thus achieving
Grid view selection and hover (#3622) This PR adds a new variant of selection, where the mouse-hovered entry is highlighted and may be selected by clicking. In the video below, we have three grid views with slightly different settings: * In the left-top corner, both hover and selection highlight is just a shape under the label. Such a grid view does not require additional layers (when compared to non-selectable grid view). * In the left-bottom corner the hover is normal shape, but selection is a _masked layer_ which allows us to have different text color. This setting requires three more layers to render. * In the right-top corner, both hover and selection are displayed in the masked layer, creating 6 additional layers. https://user-images.githubusercontent.com/3919101/181514178-f243bfeb-f2dd-4507-adc3-5344ae0579b7.mp4
2022-08-01 13:54:42 +03:00
great performance. There are variants of grid view with selection and
highlight, scrollbars, and both.
Wip/wdanilo/text shape system single scene 183406745 (#3776)
2022-11-03 10:35:06 +03:00
- [Massive improvements of text rendering performance][3776]. Different text
instances are now reusing the shape shaders and the same sprite system under
the hood. This drastically reduces the amount of required draw calls for
scenes with a lot of text.
Text rendering quality improvements. (#3855)
2022-11-08 21:15:05 +03:00
- [Text rendering quality improvements][3855]. Glyphs are now hinted in a better
way. Also, additional fine-tuning is performed per font and per host operating
system.
Focus management (#3863)
2022-11-14 12:09:49 +03:00
- [Display objects can now emit and receive events in the same style as
JavaScript DOM events][3863]. The events system implements very similar
behavior to the one described here:
https://javascript.info/bubbling-and-capturing.
Numeric slider component with variable precision (#3852) This `Slider` component allows adjusting a numeric value with the mouse. The value is increased or decreased by clicking on the component and dragging it to the left or right. The `Slider` has a configurable default value. `Ctrl`+clicking on the component resets its value to that default. When the value is moved away from the default, the value is printed in **bold**. The `Slider` precision is increased or decreased by clicking the component and dragging upward or downward. This precision influences how quickly the value changes when the mouse moves horizontally, the steps in which the value is incremented or decremented, and the number of digits used to display the value. There is a margin around the component within which the precision is not changed. Beyond this margin, the precision is increased or decreased in powers of 10 (e.g. `0.1` -> `0.01` -> `0.001` when moving the mouse downwards, or `0.1` -> `1.0` -> `10.0` when moving the mouse upwards). The margin and distance between consecutive steps along the vertical axis are configurable. The value of the `Slider` is limited to a configurable range, and cannot be adjusted beyond that range. A colored bar fills the component to indicate the current value within the range. #### Video demonstration https://user-images.githubusercontent.com/117099775/202244982-2f6f419d-7281-41f6-8607-7e492ad25b46.mp4 #### Future additions This is the first iteration of the `Slider` component. Additional features are planned for the future: * Textual editing of the value. * Improved visual feedback on precision changes. * Additional out-of-range behaviors.
2022-11-24 18:37:03 +03:00
- [Added a new component: Slider][3852]. It allows adjusting a numeric value
with the mouse. The precision of these adjustments can be increased or
decreased.
Numeric slider component enhancement (#3885) This is an enhancement of the `Slider` component implemented in #3852. It adds the following features: * Tooltips and precision change hints * Selectable slider limit behaviors * Textual slider value editing * Vertical slider layout #### Tooltips An information tooltip can now be added to a slider, it is shown when the mouse hovers over the component. Additionally, a pop-up indicating the slider's precision appears when the slider's precision has been adjusted. https://user-images.githubusercontent.com/117099775/206148098-3b4dc059-18aa-4200-9ee0-5d4382363810.mp4 #### Slider limits The previous slider implementation clamped the adjusted value to the slider's minimum/maximum limits. Now the following behaviors are available: * Hard limits: Clamp the value to a range within the slider's limits. * Soft limits: The value can extend beyond the slider's limits. When this occurs, an overflow indicator will be displayed on the side of the limit that is exceeded. * Adaptive limits: The value can extend beyond the slider's limits. When this occurs, the exceeded limit will temporarily be adjusted to double the slider's range. This will be performed iteratively until the value falls within the extended limits. When a limit is extended and the value is adjusted to fit a smaller range, the extended limit will be iteratively halved until only the necessary range is covered. The slider's extended limits will never shrink to a range smaller than the original range. These behaviors can be set to the lower and upper limits of a slider independently. https://user-images.githubusercontent.com/117099775/206148139-6149c91d-ef49-4e2d-97f6-71084f52591c.mp4 #### Textual editing The slider's value can now be entered through a text input field. Double-click to edit the slider's current value. To confirm the edit press `enter`, or press `escape` to cancel the edit. If an invalid value is entered on confirmation the slider will revert to its value before the edit. The slider's precision will be adjusted based on the number of decimal places of the value entered. https://user-images.githubusercontent.com/117099775/206148170-d3fa4c82-6e73-4b1c-9be9-cb99979f7b70.mp4 #### Vertical layout The slider component now supports a vertical layout. In this case value adjustment is performed by a vertical mouse movement, and a horizontal movement adjusts the slider's precision. The slider's track now fills the component in a vertical direction, and the slider's label is displayed near the top end of the component. https://user-images.githubusercontent.com/117099775/206148211-0f176aaf-bc1b-45e2-afd7-0d28391aafcb.mp4 #### Scroll bar mode The slider component supports two indicator modes: * `Track`: The component is filled with a colored bar from the lower limit (empty) to the upper limit (full) dependent on the slider's value. * `Thumb`: The component contains a rounded indicator that moves along the slider from one end to the other, indicating the slider's value proportionally to the slider's limits. The width of the indicator is configurable. In addition, the value text, text entry, and precision adjustment can be turned off to provide a scroll bar appearance when used with the `Thumb` indicator. https://user-images.githubusercontent.com/117099775/206148261-ae291073-85e9-4082-9f91-39b65fecdc0f.mp4 #### Example scene shortcuts The example scene contains two shortcuts in order to evaluate the dynamic addition and removal of the slider components: * `CTRL+D` drops all the slider components that are added to the scene. * `CTRL+A` adds a new set of example slider components to the scene.
2022-12-12 11:53:19 +03:00
- [Slider component functionality improvements][3885]. The slider component now
supports multiple ways to handle out-of-range values. The slider's value can
be edited as text, and a new vertical slider layout is available.
feat(183557950): Add ProjectsGrid View for Cloud Dashboard (#3857) This PR is a draft PR while I learn EnsoGL. The eventual goal is to implement the projects list portion of the cloud dashboard in this PR. This PR will implement part of https://www.pivotaltracker.com/n/projects/2539513/stories/183557950 ### Important Notes This PR is still really rough and contains a lot of hacks & hard-coded values. The FRP usage is also likely to be suboptimal and need fixing.
2022-12-04 07:41:56 +03:00
- [Added ProjectsGrid view for Cloud Dashboard][3857]. It provides the first
steps towards migrating the Cloud Dashboard from the existing React (web-only)
implementation towards a shared structure that can be used in both the Desktop
and Web versions of the IDE.
chore(183909391): Remove existing Cloud dashboard code (#4047) * chore(183909391): Remove Cloud dashboard * update changelog
2023-01-18 10:46:48 +03:00
- [Removed Cloud Dashboard][4047]. The Cloud Dashboard was being rewritten in
EnsoGL but after internal discussion we've decided to rewrite it in React,
with a shared implementation between the Desktop and Web versions of the IDE.
Grid-view based dropdown component (#3985) Implements https://www.pivotaltracker.com/n/projects/2539304/stories/184023380 Dropdown component. Planned to be used in nodes as a single and multiple selection widget, both for static and dynamically loaded values. Initial support is focused on static data, with limited support for dynamic sources. Notably, loading states are not supported yet. Full support for that is planned to be added later with widget lazy-loading. - Supports single and multiple selections. - Dedicated API for providing a static list of all entries. - Range-based query API for dynamically loading data as it is scrolled (only basic support - will need more work for proper async lazy-loading). - Internal entry cache and query batching to avoid querying data one by one (the batching for now is very basic, will have to be improved for proper lazy-loading). - Automatic dropdown width adjustment based on the entry label lengths, up to a set max allowed value. - Open and close animation. - Keyboard support for focusing and selecting entries. ![image](https://user-images.githubusercontent.com/919491/207866293-de2e3fef-c93b-48cc-8253-11c186d223fd.png) # Important Notes Implementing the dropdown on top of grid-view have uncovered some assumptions around grid-view layers. It was assumed to always be a part of the component browser. Removing that assumption required a mechanism for propagating camera update information through layer tree. This is now implemented using a `camera_parent` layer field. Ideally each layer should simply have at most a single parent, and camera inheritance would follow that. That refactor turned out to be quite involved, so right now the simpler temporary solution is introduced in order to not delay this PR further.
2022-12-22 21:19:40 +03:00
- [Added a new component: Dropdown][3985]. A list of selectable labeled entries,
suitable for single and multi-select scenarios.
Shaders precompilation (#4003)
2023-01-27 03:09:09 +03:00
- [Compile-time shader optimizer was implemented][4003]. It is capable of
extracting non-optimized shaders from the compiled WASM artifacts, running
stand-alone optimization toolchain (glslc, spirv-opt, spirv-cross), and
injecting optimized shaders back to WASM during its initialization process.
Unfortunately, it caused our theme system to stop working correctly, because
generated shaders differ per theme (only light theme is available, the dark
theme has been disabled). We will support multiple themes in the future, but
this is not on our priority list right now.
Improving Performance Monitor (#5895)
2023-03-21 11:17:54 +03:00
- [Performance monitor was extended with the ability to print details of actions
performed in a given frame][5895]. In particular, you can now inspect names of
all symbols rendered in a given frame. You can also pause the performance
monitor and inspect results recorded in the past.
Add tooltips to the action bar (#6035) Implements #5933: adding tooltips to the buttons next to nodes. To make the UI consistent, I've added tooltips to the `ToggleButton` class directly, since whenever you have an icon button, it seems helpful to have a tooltip. `ToggleButton` is only used for the profiling button in the top-right corner and the buttons next to nodes. The output context switch button [isn't implemented yet](https://github.com/enso-org/enso/issues/5929), but once it is, adding a tooltip should be one-liner. ![Recording 2023-03-22 at 17 21 58](https://user-images.githubusercontent.com/607786/226972920-81033b37-001f-49eb-9fc6-453120f01760.gif)
2023-03-27 20:02:06 +03:00
- [ToggleButtons can now have tooltips][6035].
Make tooltips more visually pleasing (#6097) Closes #6059: visually centering text and adding a longer delay before showing tooltips. See the commit messages for details. ![Recording 2023-03-28 at 09 43 17](https://user-images.githubusercontent.com/607786/228164744-5a3ae878-11ab-4cdd-8fdf-93bdf4fe84fe.gif)
2023-03-30 11:51:31 +03:00
- [Rendering of tooltips was improved.][6097] Their text is now more vertically
centered and the delay before showing them was extended.
Dynamic app resampling and better performance measurements. (#6595)
2023-05-29 02:42:42 +03:00
- [Accurate GPU performance measurements have been implemented][6595]. It is
possible now to track both the time spent on both the CPU and the GPU sides.
feat(183557950): Add ProjectsGrid View for Cloud Dashboard (#3857) This PR is a draft PR while I learn EnsoGL. The eventual goal is to implement the projects list portion of the cloud dashboard in this PR. This PR will implement part of https://www.pivotaltracker.com/n/projects/2539513/stories/183557950 ### Important Notes This PR is still really rough and contains a lot of hacks & hard-coded values. The FRP usage is also likely to be suboptimal and need fixing.
2022-12-04 07:41:56 +03:00
[3857]: https://github.com/enso-org/enso/pull/3857
Grid-view based dropdown component (#3985) Implements https://www.pivotaltracker.com/n/projects/2539304/stories/184023380 Dropdown component. Planned to be used in nodes as a single and multiple selection widget, both for static and dynamically loaded values. Initial support is focused on static data, with limited support for dynamic sources. Notably, loading states are not supported yet. Full support for that is planned to be added later with widget lazy-loading. - Supports single and multiple selections. - Dedicated API for providing a static list of all entries. - Range-based query API for dynamically loading data as it is scrolled (only basic support - will need more work for proper async lazy-loading). - Internal entry cache and query batching to avoid querying data one by one (the batching for now is very basic, will have to be improved for proper lazy-loading). - Automatic dropdown width adjustment based on the entry label lengths, up to a set max allowed value. - Open and close animation. - Keyboard support for focusing and selecting entries. ![image](https://user-images.githubusercontent.com/919491/207866293-de2e3fef-c93b-48cc-8253-11c186d223fd.png) # Important Notes Implementing the dropdown on top of grid-view have uncovered some assumptions around grid-view layers. It was assumed to always be a part of the component browser. Removing that assumption required a mechanism for propagating camera update information through layer tree. This is now implemented using a `camera_parent` layer field. Ideally each layer should simply have at most a single parent, and camera inheritance would follow that. That refactor turned out to be quite involved, so right now the simpler temporary solution is introduced in order to not delay this PR further.
2022-12-22 21:19:40 +03:00
[3985]: https://github.com/enso-org/enso/pull/3985
Shaders precompilation (#4003)
2023-01-27 03:09:09 +03:00
[4003]: https://github.com/enso-org/enso/pull/4003
Add cloud dashboard to changelog (#6688)
2023-05-18 00:20:49 +03:00
[4047]: https://github.com/enso-org/enso/pull/4047
Improving Performance Monitor (#5895)
2023-03-21 11:17:54 +03:00
[5895]: https://github.com/enso-org/enso/pull/5895
Add tooltips to the action bar (#6035) Implements #5933: adding tooltips to the buttons next to nodes. To make the UI consistent, I've added tooltips to the `ToggleButton` class directly, since whenever you have an icon button, it seems helpful to have a tooltip. `ToggleButton` is only used for the profiling button in the top-right corner and the buttons next to nodes. The output context switch button [isn't implemented yet](https://github.com/enso-org/enso/issues/5929), but once it is, adding a tooltip should be one-liner. ![Recording 2023-03-22 at 17 21 58](https://user-images.githubusercontent.com/607786/226972920-81033b37-001f-49eb-9fc6-453120f01760.gif)
2023-03-27 20:02:06 +03:00
[6035]: https://github.com/enso-org/enso/pull/6035
Make tooltips more visually pleasing (#6097) Closes #6059: visually centering text and adding a longer delay before showing tooltips. See the commit messages for details. ![Recording 2023-03-28 at 09 43 17](https://user-images.githubusercontent.com/607786/228164744-5a3ae878-11ab-4cdd-8fdf-93bdf4fe84fe.gif)
2023-03-30 11:51:31 +03:00
[6097]: https://github.com/enso-org/enso/pull/6097
Add cloud dashboard to changelog (#6688)
2023-05-18 00:20:49 +03:00
[6130]: https://github.com/enso-org/enso/pull/6130
Show error pop-up when failing to rename a project (#6366) Closes #5065: when a project can't be renamed, it now shows an error pop-up and stays in edit mode. https://user-images.githubusercontent.com/607786/234025360-6761f7d6-c13c-479c-a0ba-8af5d81f6e87.mp4
2023-05-08 13:12:26 +03:00
[6366]: https://github.com/enso-org/enso/pull/6366
Finishing Vector Editor (#6470)
2023-05-02 12:24:20 +03:00
[6341]: https://github.com/enso-org/enso/pull/6341
[6470]: https://github.com/enso-org/enso/pull/6470
Dynamic app resampling and better performance measurements. (#6595)
2023-05-29 02:42:42 +03:00
[6595]: https://github.com/enso-org/enso/pull/6595
Add cloud dashboard to changelog (#6688)
2023-05-18 00:20:49 +03:00
[6487]: https://github.com/enso-org/enso/pull/6487
Implement loading spinner for visualisations. (#6512) Fixes #5088. Adds a ensoGL spinner for visualizations waiting on data. https://user-images.githubusercontent.com/1428930/236801655-67a0ffed-da5d-4e27-8797-cd8126cb86d9.mp4 # Important Notes This spinner will not show up for the duration where visualizations are processing data on the frontend. If this is a concern, visualization need to implement heir own loading spinner, or we need to provide a unified API for them to keep the spinner visible.
2023-05-12 07:41:55 +03:00
[6512]: https://github.com/enso-org/enso/pull/6512
SDF-based mechanism for making letters bold (#3385) Fixes [181641027](https://www.pivotaltracker.com/story/show/181641027). There are new methods of text::Area for making some letters bolder, without moving them nor any other letters in the line. Tested on DejaVuSans text: ![image](https://user-images.githubusercontent.com/3919101/162199723-524f7560-535f-4c98-bcb4-6b760ad8cb04.png) ![image](https://user-images.githubusercontent.com/3919101/162199806-e6582c56-3071-4653-8ad2-114df86cd6b7.png) ![image](https://user-images.githubusercontent.com/3919101/162199880-1836e902-8663-4696-bcb7-2b15c3c243c6.png) On MacOS: <img width="824" alt="Screenshot 2022-04-07 at 14 54 40" src="https://user-images.githubusercontent.com/3919101/162203730-ffda3096-7aab-443f-a45a-bfa18784ba36.png"> <img width="379" alt="Screenshot 2022-04-07 at 14 54 52" src="https://user-images.githubusercontent.com/3919101/162203751-f5ca2e26-fdb6-4521-9821-999111b80ac0.png"> <img width="160" alt="Screenshot 2022-04-07 at 14 54 58" src="https://user-images.githubusercontent.com/3919101/162203769-3c367f81-67bb-48aa-994c-42eeb131017e.png">
2022-04-12 20:39:08 +03:00
The user should be able to remove duplicate elements from a Vector (#3224)
2022-01-17 12:51:56 +03:00
#### Enso Standard Library
- [Implemented `Vector.distinct` allowing to remove duplicate elements from a
Vector][3224]
Moving distinct to Map (#3229) * Moving distinct to Map * Mixed Type Comparable Wrapper * Missing Bracket Still an issue with `Integer` in the mixed vector test * PR comments * Use naive approach for mixed types * Enable pending test * Performance timing function * Handle incomparable types cleanly * Tidy up the time_execution function * PR comments. * Change log
2022-01-25 12:57:30 +03:00
- [Implemented `Duration.time_execution` allowing timing of the execution of an
misc: fix changelog formatting (#3263)
2022-02-10 11:09:13 +03:00
expression within the UI][3229]
Improve Vector (#3232)
2022-01-25 20:29:39 +03:00
- [Improved performance of `Vector.filter` and `Vector.each`; implemented
`Vector.filter_with_index`. Made `Vector.at` accept negative indices and
ensured it fails with a dataflow error on out of bounds access instead of an
internal Java exception.][3232]
Data analysts should be able to transform a Table using the select_columns function (#3230) * Utility for mapping errors and warnings * Imlpement By_Index * Expose select_columns in InMem and DB. Need testing * checkpoint: writing tests * Fix minor issues, mock warning mapping for testing purposes * Improve By_Index error handling * A helper for testing problem handling * More error handling * docs * changelog * Fix matching test * Add SQLite tests * cleanup after test * Rework problem handling * small refactor * add examples * Add more test cases for regex matching * Fix Regex.Patter.matches to match full string * "Fix" tests
2022-02-02 12:04:06 +03:00
- [Implemented the `Table.select_columns` operation.][3230]
Data analysts should be able to transform a Table using the remove_columns and reorder_columns functions (#3240)
2022-02-03 17:18:47 +03:00
- [Implemented the `Table.remove_columns` and `Table.reorder_columns`
operations.][3240]
Data analysts should be able to reorder columns into name order using sort_columns functions (#3250)
2022-02-08 19:28:46 +03:00
- [Implemented the `Table.sort_columns` operation.][3250]
Fix vector sorting with TCO comparators (#3256)
2022-02-10 00:17:43 +03:00
- [Fixed `Vector.sort` to handle tail-recursive comparators][3256]
Data analysts should be able to transform a Table using the rename_columns functions (#3249) * Implement Natural_Order and sort_columns * Starting on Rename Align Column_Mapping Add By_Position Separating off the validation for By_Index so can reuse for rename By_Position implemented By_Index implemented Adjusted behaviour following discussion with Ned, so that renames dominate untouched columns. Moving to validation style checks for problems Putting accumulator back Rename work * Add Range.find * More work * Regex support Tidy of Unique Name Strategy * Fix Regex support * Warning messages Tests for Unique Naming Strategy Table rename working * Database Table rename_columns Fix for Table **Must follow up on slice** * Some tests * More tests * Complete test set (and associated fixes) * Functional use_first_row_as_names Tests to go... * Test for use_first_row_as_names * Change log * trailing space Co-authored-by: Radosław Waśko <radoslaw.wasko@enso.org>
2022-02-11 13:18:51 +03:00
- [Implemented `Range.find`, `Table.rename_columns` and
`Table.use_first_row_as_names` operations][3249]
Adding Text.at and Text.is_digit functions (#3269) * Add Text.at function * Add tests for Text.at * Add tests for Text.is_digit * Change log * Avoid memory allocation
2022-02-14 12:03:55 +03:00
- [Implemented `Text.at` and `Text.is_digit` methods][3269]
Properly expose stacktraces and related data to user code (#3271)
2022-02-16 10:36:19 +03:00
- [Implemented `Runtime.get_stack_trace` together with some utilities to process
stack traces and code locations][3271]
Implement Vector.flatten (#3259)
2022-02-15 18:16:08 +03:00
- [Implemented `Vector.flatten`][3259]
Improvement to the Natural Order Sort (#3276) * Improved Natural Order Data generator for benchmarking * Missing Import Benchmark script * Update Natural_Order.enso Restore missing ToDo * Changelog * PR Comments * PR Comments * Additional comments. * Correction
2022-02-16 20:40:33 +03:00
- [Significant performance improvement in `Natural_Order` and new `Faker`
methods added to `Standard.Test`][3276]
Adding Integer.Parse (#3283) * Integer parse via Longs * Integer parse via Longs * Benchmark for Number Parse * CHANGELOG.md and Natural Order * Expanded test set * Number base tests * Few more negative tests
2022-02-17 18:04:00 +03:00
- [Implemented `Integer.parse`][3283]
Ensure that `Text.compare_to` compares strings according to grapheme clusters (#3282) https://www.pivotaltracker.com/story/show/181175238
2022-02-17 20:09:41 +03:00
- [Made `Text.compare_to` correctly handle Unicode normalization][3282]
Data analysts should be able to use `Text.contains` to check for substring using various matcher techniques. (#3285) * Add matching mode definitions * Add stub for new method API and an initial test suite * Fix tests, implement exact matching * Implement Regex matching * changelog * Add benchmarks * Wokraround for case insensitive regex locale support * minor tweaks * Unify Case_Insensitive * Update edge cases * Fix other affected places * minor style change * Add a problematic test * Add a regex test for a similar situation * Migrate to StringSearch:wq * Add test cases for scharfes S edge case * Add problematic Regex Unicode normalization test * Document the regex accents peculiarity * Do not apply the normalization in ASCII only mode * cr
2022-02-22 18:41:56 +03:00
- [Extend `Text.contains` API to support regex and case insensitive
search.][3285]
Text.take and Text.drop (#3287) Implementation of the Text take and drop APIs - Added `Range.contains` function - Added `Text_Sub_Range` type - Added `Text_Utils.index_of` and `Text_Utils.last_index_of` based on ICU StringSearcher
2022-02-22 21:50:59 +03:00
- [Implemented new `Text.take` and `Text.drop` functions, replacing existing
functions][3287]
Data analysts should be able to use `Text.starts_with` and `Text.ends_with` (#3292) Implements https://www.pivotaltracker.com/story/show/181265900
2022-02-23 19:48:33 +03:00
- [Implemented new `Text.starts_with` and `Text.ends_with` functions, replacing
existing functions][3292]
Data analysts should be able to use `Text.to_case` to change the case of Text values (#3302) * Move to_upper_case and to_lower_case into to_case * Add an export, not sure about it * Implement title case TODO: some more tests would be good * Add more tests * explain title case * fix todo * changelog
2022-03-01 02:20:41 +03:00
- [Implemented `Text.to_case`, replacing `Text.to_lower_case` and
`Text.to_upper_case`][3302]
Table.group_by (#3305) Functioning group_by based of Enso Map. # Important Notes This is an initial version which will be used to establish the API. The grouping map will need to be moved to Java code for performance.
2022-03-01 19:18:11 +03:00
- [Implemented initial `Table.group_by` function on Standard.Table][3305]
Text.pad and Text.trim (#3309) Implements https://www.pivotaltracker.com/story/show/181265516
2022-03-02 20:19:39 +03:00
- [Implemented `Text.pad` and `Text.trim`][3309]
Updating `Text.repeat` and adding `Text.*` (#3310) Updating the `Text.repeat` function: - fix issue with negative count - add * operator Add tests of the function.
2022-03-02 22:00:47 +03:00
- [Updated `Text.repeat` and added `*` operator shorthand][3310]
Within Vector, use Array.Copy wherever possible (#3236) Following the Slice and Array.Copy experiment, took just the Array.Copy parts out and built into the Vector class. This gives big performance wins in common operations: | Test | Ref | New | | --- | --- | --- | | New Vector | 41.5 | 41.4 | | Append Single | 26.6 | 4.2 | | Append Large | 26.6 | 4.2 | | Sum | 230.1 | 99.1 | | Drop First 20 and Sum | 343.5 | 96.9 | | Drop Last 20 and Sum | 311.7 | 96.9 | | Filter | 240.2 | 92.5 | | Filter With Index | 364.9 | 237.2 | | Partition | 772.6 | 280.4 | | Partition With Index | 912.3 | 427.9 | | Each | 110.2 | 113.3 | *Benchmarks run on an AWS EC2 r5a.xlarge with 1,000,000 item count, 100 iteration size run 10 times.* # Important Notes Have generally tried to push the `@Tail_Call` down from the Vector class and move to calling functions on the range class. - Expanded benchmarks on Vector - Added `take` method to Vector - Added `each_with_index` method to Vector - Added `filter_with_index` method to Vector
2022-03-03 18:40:48 +03:00
- [General improved Vector performance and new `Vector.each_with_index`,
`Vector.fold_with_index` and `Vector.take` methods.][3236]
New Text.insert function (#3311) Implements https://www.pivotaltracker.com/n/projects/2539304
2022-03-04 18:40:34 +03:00
- [Implemented new `Text.insert` method][3311]
Added `compare_to` to True/False (#3317)
2022-03-08 16:24:04 +03:00
- [Implemented `Bool.compare_to` method][3317]
Restructuring the Faker type and creating tests for Group_By (#3318) - Added Minimum, Maximum, Longest. Shortest, Mode, Percentile - Added first and last to Map - Restructured Faker type more inline with FakerJS - Created 2,500 row data set - Tests for group_by - Performance tests for group_by
2022-03-09 13:31:02 +03:00
- [Implemented `Map.first`, `Map.last` functions. Expanded `Table.group_by` to
also compute mode, percentile, minimum, maximum.][3318]
Data analysts should be able to use `Text.location_of` to find indexes within string using various matchers (#3324) Implements https://www.pivotaltracker.com/n/projects/2539304/stories/181266029
2022-03-12 22:42:00 +03:00
- [Implemented `Text.location_of` and `Text.location_of_all` methods.][3324]
Refactor table.group_by to table.aggregate (#3339) Following UX work move to `table.aggregate` function.
2022-03-15 17:23:36 +03:00
- [Replaced `Table.group_by` with `Table.aggregate`][3339]
The library developer should be able to handle specific types of Panics while passing through others (#3344) Implements https://www.pivotaltracker.com/story/show/181569176 Also ensures that Dataflow Errors have proper stack traces (earlier they did not point at the right location).
2022-03-18 19:57:06 +03:00
- [Implemented `Panic.catch` and helper functions for handling errors. Added a
type parameter to `Panic.recover` to recover specific types of errors.][3344]
Refactor Aggregate Column (#3349) - Make it easier to understand the computations. - Fix issue with First. - Improve quote handling in Concatenate - Added validation and warnings to input
2022-03-22 21:18:46 +03:00
- [Added warning handling to `Table.aggregate`][3349]
Extend Aggregate_Spec test suite with tests for missed edge-cases to ensure the feature is well-tested on all backends (#3383) Implements https://www.pivotaltracker.com/story/show/181805693 and finishes the basic set of features of the Aggregate component. Still not all aggregations are supported everywhere, because for example SQLite has quite limited support for aggregations. Currently the workaround is to bring the table into memory (if possible) and perform the computation locally. Later on, we may add more complex generator features to emulate the missing aggregations with complex sub-queries.
2022-04-12 14:02:01 +03:00
- [Improved performance of `Table.aggregate` and full warnings
implementation][3364]
Data analysts should be able to reverse strings using `Text.reverse` (#3377) This commit implements `Text.reverse` as an extension on `Text`. `Text.reverse` reverses strings. For example: `"Hello World!".reverse` results in `"!dlroW olleH"`. Strings are reversed by their Extended Grapheme Clusters not by their characters. This has some performance implications because we need to find these grapheme cluster boundaries when iterating. To do so, `BreakIterator.getCharacterInstance` is used. Implements: https://www.pivotaltracker.com/n/projects/2539304/stories/181265419
2022-04-05 19:45:56 +03:00
- [Implemented `Text.reverse`][3377]
Extend Aggregate_Spec test suite with tests for missed edge-cases to ensure the feature is well-tested on all backends (#3383) Implements https://www.pivotaltracker.com/story/show/181805693 and finishes the basic set of features of the Aggregate component. Still not all aggregations are supported everywhere, because for example SQLite has quite limited support for aggregations. Currently the workaround is to bring the table into memory (if possible) and perform the computation locally. Later on, we may add more complex generator features to emulate the missing aggregations with complex sub-queries.
2022-04-12 14:02:01 +03:00
- [Implemented support for most Table aggregations in the Database
backend.][3383]
Data analysts should be able to use `Text.replace` to substitute parts of the text (#3393) Implements https://www.pivotaltracker.com/story/show/181266274
2022-04-13 22:21:47 +03:00
- [Update `Text.replace` to new API.][3393]
Restructuring for File.read (#3390) - Added Encoding type - Added `Text.bytes`, `Text.from_bytes` with Encoding support - Renamed `File.read` to `File.read_text` - Renamed `File.write` to `File.write_text` - Added Encoding support to `File.read_text` and `File.write_text` - Added warnings to invalid encodings
2022-04-19 19:50:03 +03:00
- [Add encoding support to `Text.bytes` and `Text.from_bytes`. Renamed and added
encoding to `File.read_text`. New `File.read` API.][3390]
Review Range and Interval, resolve infinite loop issue (#3408) Implements: https://www.pivotaltracker.com/story/show/181652841
2022-04-20 19:22:01 +03:00
- [Improved the `Range` type. Added a `down_to` counterpart to `up_to` and
`with_step` allowing to change the range step.][3408]
Data analysts should be able to use `Text.split`, `Text.lines` and `Text.words` to break up strings (#3415) Implements https://www.pivotaltracker.com/story/show/181266184 ### Important Notes Changed example image download to only proceed if the file did not exist before - thus cutting on the build time (the build used to download it _every_ time - which completely failed the build if network is down). A redownload can be forced by performing a fresh repository checkout.
2022-04-26 18:22:53 +03:00
- [Aligned `Text.split` API with other methods and added `Text.lines`.][3415]
Improve support for reading Delimited files (#3424) Implements https://www.pivotaltracker.com/story/show/181823957
2022-04-29 20:12:19 +03:00
- [Implemented a basic reader for the `Delimited` file format.][3424]
File_Format.Excel work (#3425) - Read in Excel files following the specification. - Support for XLSX and XLS formats. - Ability to select ranges and sheets. - Skip Rows and Row Limits. # Important Notes - Minor fix to DelimitedReader for Windows
2022-05-06 16:21:10 +03:00
- [Implemented a reader for the `Excel` file format.][3425]
Delimited File Encoding (#3430) Implements https://www.pivotaltracker.com/story/show/181998375
2022-05-11 01:44:05 +03:00
- [Added custom encoding support to the `Delimited` file format reader.][3430]
Statistics on a Vector (#3442) - Implements various statistics on Vector # Important Notes Some minor codebase improvements: - Some tweaks to Any/Nothing to improve performance - Fixed bug in ObjectComparator - Added if_nothing - Removed Group_By_Key
2022-05-11 16:25:06 +03:00
- [Implemented `compute` method on `Vector` for statistics calculations.][3442]
Cleanup Ref - get/put (#3457) The change promotes static methods of `Ref`, `get` and `put`, to be methods of `Ref` type. The change also removes `Ref` module from the default namespace. Had to mostly c&p functional dispatch for now, in order for the methods to be found. Will auto-generate that code as part of builtins system. Related to https://www.pivotaltracker.com/story/show/182138899
2022-05-17 13:26:36 +03:00
- [Promote get and put to be methods of Ref type rather than of Ref
module][3457]
Parsing values with known types (#3455) Implements https://www.pivotaltracker.com/story/show/181824146
2022-05-18 18:27:48 +03:00
- [Implemented `Table.parse_values`, parsing text columns according to a
specified type.][3455]
Refactor methods of Managed_Resource (#3460) Promoted `with`, `take`, `finalize` to be methods of Managed_Resource rather than static methods always taking `resource`, for consistency reasons. This required function dispatch boilerplate, similarly to `Ref`. In future iterations we will address this boilerplate code. Related to https://www.pivotaltracker.com/story/show/182212217
2022-05-18 20:27:42 +03:00
- [Promote with, take, finalize to be methods of Managed_Resource
instance][3460]
Automatic inference of value types when parsing table columns (#3462) Implements https://www.pivotaltracker.com/story/show/182199966
2022-05-20 18:08:36 +03:00
- [Implemented automatic type detection for `Table.parse_values`.][3462]
Integrate value parsing with Delimited file reading (#3463) Implements https://www.pivotaltracker.com/story/show/182200028
2022-05-24 18:59:00 +03:00
- [Integrated value parsing with the `Delimited` file reader.][3463]
The user should be able to have the headers Inferred when reading a Delimited file (#3472) Implements https://www.pivotaltracker.com/story/show/181986831
2022-05-25 16:29:17 +03:00
- [Implemented the `Infer` setting for headers in the `Delimited` file format
and made it the default.][3472]
Implement Table from Text conversion (#3478) Implements https://www.pivotaltracker.com/story/show/181824168
2022-05-26 15:04:25 +03:00
- [Implemented a `Table.from Text` conversion allowing to parse strings
representing `Delimited` files without storing them on the filesystem.][3478]
Rank Data, Correlation, Covariance, R Squared (#3484) - Added new `Statistic`s: Covariance, Pearson, Spearman, R Squared - Added `covariance_matrix` function - Added `pearson_correlation` function to compute correlation matrix - Added `rank_data` and Rank_Method type to create rankings of a Vector - Added `spearman_correlation` function to compute Spearman Rank correlation matrix # Important Notes - Added `Panic.throw_wrapped_if_error` and `Panic.handle_wrapped_dataflow_error` to help with errors within a loop. - Removed `Array.set_at` use from `Table.Vector_Builder`
2022-05-30 20:13:06 +03:00
- [Added rank data, correlation and covariance statistics for `Vector`][3484]
Implement `Table.order_by` for SQLite and the common scaffolding for all backends (#3502) Implements the common and SQLite parts of https://www.pivotaltracker.com/story/show/182195405
2022-06-06 13:56:52 +03:00
- [Implemented `Table.order_by` for the SQLite backend.][3502]
Improve database `Table.order_by` (#3514) Implements https://www.pivotaltracker.com/story/show/182195405 Adds support for the Postgres dialect and simple case insensitive collation for SQLite.
2022-06-07 15:31:55 +03:00
- [Implemented `Table.order_by` for the PostgreSQL backend.][3514]
Implement In-Memory Table order_by (#3515) Implemented the `order_by` function with support for all modes of operation. Added support for case insensitive natural order. # Important Notes - Improved MultiValueIndex/Key to not create loads of arrays. - Adjusted HashCode for MultiValueKey to have a simple algorithm. - Added Text_Utils.compare_normalized_ignoring_case to allow for case insensitive comparisons. - Fixed issues with ObjectComparator and added some unit tests for it.
2022-06-08 15:30:50 +03:00
- [Implemented `Table.order_by` for the in-memory table.][3515]
Basic changes to File_Format (#3516) Implements https://www.pivotaltracker.com/story/show/182308987
2022-06-08 12:53:18 +03:00
- [Renamed `File_Format.Text` to `Plain_Text`, updated `File_Format.Delimited`
API and added builders for customizing less common settings.][3516]
Adjusting First and Last order_by to use Sort_Column_Selector (#3517)
2022-06-10 12:59:03 +03:00
- [Allow control of sort direction in `First` and `Last` aggregations.][3517]
Add `Text.write` Function (#3518) Implements https://www.pivotaltracker.com/story/show/182309026
2022-06-13 12:11:46 +03:00
- [Implemented `Text.write`, replacing `File.write_text`.][3518]
New set function, parse a column (#4097) - New `set` function design - takes a `Column` and works with that more easily and supports control of `Set_Mode`. - New simple `parse` API on `Column`. - Separated expression support for `filter` to new `filter_by_expression` on `Table`. - New `compute` function allowing creation of a column from an expression. - Added case sensitivity argument to `Column` based on `starts_with`, `ends_with` and `contains`. - Added case sensitivity argument to `Filter_Condition` for `Starts_With`, `Ends_With`, `Contains` and `Not_Contains`. - Fixed the issue in JS Table visualisation where JavaScript date was incorrectly set. - Some dynamic dropdown expressions - experimenting with ways to use them. - Fixed issue with `.pretty` that wasn't escaping `\`. - Changed default Postgres DB to `postgres`. - Fixed SQLite support for starts_with, ends_with and contains to be consistent (using GLOB not LIKE).
2023-01-31 23:48:16 +03:00
- [Removed obsolete `select`, `group`, `sort` and releated types from
tables.][3519]
Update Excel reading API (#3523) - Remove `from_xls` and `from_xlsx`. - Add `headers` support to `File_Format.Excel`. - Altered default read for Excel to be the first sheet. - Altered behavior so that single cells grow down and right when reading sheet. - Altered `Excel_Range` so knows if single cell or 1x1 range address. # Important Notes - Renamed `Range` to `Cell_Range` to avoid name clash.
2022-06-21 16:39:32 +03:00
- [Removed obsolete `from_xls` and `from_xlsx` functions. Added support for
reading column names from first row in `File_Format.Excel`][3523]
Implement value formatting and writing new files in Delimited format. (#3528) Implements https://www.pivotaltracker.com/story/show/182309429 and https://www.pivotaltracker.com/story/show/182309573
2022-06-23 19:51:52 +03:00
- [Added `File_Format.Delimited` support to `Table.write` for new files.][3528]
Update `Database.connect` to match new API (#3542) Initial work restructuring the `Database.connect` API - New SQLite API with support for InMemory. - Updated PostgreSQL API with SSL and Client Certificate Support. - Updated Redshift API. # Important Notes Follow up tasks: - PostgreSQL SSL additional testing. - Driver version updating. - `.pgpass` support.
2022-07-04 23:26:44 +03:00
- [Adjusted `Database.connect` API to new design.][3542]
Adding write support to `File_Format.Excel` (#3551) Support for writing tables to Excel. # Important Notes Has custom support for Error mode as will allow appending a new table in this mode to the file.
2022-07-04 21:32:16 +03:00
- [Added `File_Format.Excel` support to `Table.write` for new files.][3551]
Implementing basic functions (#3554) The language specification suggests to add [five basic functions into the standard library](https://github.com/enso-org/design/blob/wip/wd/enso-spec/epics/enso-spec-1.0/05.%20Functions.md#useful-functions-in-the-standard-library). `identity`, `flip`, `const`, `curry` & `uncurry`. # Important Notes The new functions are being added into existing `Function.enso` file. That may not be the best place, but it is not clear from the [design spec](https://github.com/enso-org/design/blob/wip/wd/enso-spec/epics/enso-spec-1.0/05.%20Functions.md#useful-functions-in-the-standard-library) how they are supposed to be imported. I can move them wherever needed. There is a documentation provided for each of the functions, but I am not sure how to verify it is correct. Do we generate the documentation for stdlib somehow?
2022-07-11 13:30:44 +03:00
- [identity,const,flip,curry,uncurry functions][3554]
Adding Append support to Excel.Write (#3558) Adds support for appending to an existing Excel table. # Important Notes - Renamed `Column_Mapping` to `Column_Name_Mapping` - Changed new type name to `Map_Column` - Added last modified time and creation time to `File`.
2022-07-07 09:41:33 +03:00
- [Added append support for `File_Format.Excel`.][3558]
Custom Encoding support when writing Delimited files (#3564) Implements https://www.pivotaltracker.com/story/show/182545847
2022-07-07 03:20:00 +03:00
- [Added support for custom encodings in `File_Format.Delimited` writing.][3564]
Allow filtering caught error type in `Error.catch` (#3574) More and more often I need a way to only recover a specific type of a dataflow error (in a similar manner as with panics). So the API for `Error.catch` has been amended to more closely resemble `Panic.catch`, allowing to handle only specific types of dataflow errors, passing others through unchanged. The default is `Any`, meaning all errors are caught by default, and the behaviour of `x.catch` remains unchanged.
2022-07-11 11:26:44 +03:00
- [Allow filtering caught error type in `Error.catch`.][3574]
Add appending support for Delimited files (#3573) Implements https://www.pivotaltracker.com/story/show/182309839
2022-07-11 15:36:01 +03:00
- [Implemented `Append` mode for `File_Format.Delimited`.][3573]
Move `write_bytes` to be part of `Vector`. (#3583) Updates `write_bytes` API to be part of `Vector` and to conform to `write` APIs. # Important Notes Ensures doesn't touch the file if an invalid byte array.
2022-07-14 14:30:40 +03:00
- [Added `Vector.write_bytes` function and removed old `File.write_bytes`][3583]
Add new options to the Delimited format (#3581) Implements https://www.pivotaltracker.com/story/show/182662195 and https://www.pivotaltracker.com/story/show/182651884
2022-07-14 18:01:26 +03:00
- [Added `line_endings` and `comment_character` options to
`File_Format.Delimited`.][3581]
Type name case fixes: (#3590) - MacOS => Mac_OS - PostgreSQL => Postgres - SQLite => SQLite (align a few) - InMemory => In_Memory - PointData => Point_Data - Io_Error => IO_Error - Standard.Table.Io => Standard.Table.IO In Tests: - MyError => My_Error - NotFoo => Not_Foo
2022-07-19 17:09:09 +03:00
- [Fixed the case of various type names and library paths][3590]
Add support for `.pgpass` to PostgreSQL (#3593) Implements https://www.pivotaltracker.com/story/show/182582924
2022-07-21 16:32:37 +03:00
- [Added support for parsing `.pgpass` file and `PG*` environment variables for
the Postgres connection][3593]
Add Linear Regression support for Vectors. (#3601) Adds least squares regression APIs. Covers the basic 4 trend line types from Excel (doesn't cover Polynomial or Moving Average). Removes the old `Model` from the `Standard.Table`.
2022-07-22 11:41:17 +03:00
- [Added `Regression` to the `Standard.Base` library and removed legacy `Model`
type from `Standard.Table`.][3601]
Create `Index_Sub_Range` type and update `Text.take` and `Text.drop` (#3617)
2022-08-03 14:41:34 +03:00
- [Created `Index_Sub_Range` type and updated `Text.take` and
`Text.drop`.][3617]
Use Vector.from_polyglot_array to make Vectors backed by polyglot arrays (#3628) Use Proxy_Polyglot_Array as a proxy for polyglot arrays, thus unifying the way the underlying array is accessed in Vector. Used the opportunity to cleanup builtin lookup, which now actually respects what is defined in the body of @Builtin_Method annotation. Also discovered that polyglot null values (in JS, Python and R) were leaking to Enso. Fixed that by doing explicit translation to `Nothing`. https://www.pivotaltracker.com/story/show/181123986
2022-08-24 00:13:16 +03:00
- [Added `Vector.from_polyglot_array` to make `Vector`s backed by polyglot
Arrays][3628]
Add `Vector.take` and `Vector.drop` functions (#3629) Implements https://www.pivotaltracker.com/story/show/182307048
2022-08-10 19:02:02 +03:00
- [Updated `Vector.take` and `Vector.drop` and removed their obsolete
counterparts.][3629]
Short hand version for `order_by` (#3643) Implements https://www.pivotaltracker.com/story/show/182868310
2022-08-16 18:41:37 +03:00
- [Short-hand syntax for `order_by` added.][3643]
Add key functions to Table to make it act as [Column] (#3644) Implements https://www.pivotaltracker.com/story/show/181370836
2022-08-18 15:33:02 +03:00
- [Expanded `Table.at` to support index access and added `Table.column_count`
method.][3644]
Remove `Array.set_at` (#3634) Implements https://www.pivotaltracker.com/story/show/182879865 # Important Notes Note that removing `set_at` still does not make our arrays fully immutable - `Array.copy` can still be used to mutate them.
2022-08-26 12:34:33 +03:00
- [Removed `Array.set_at`.][3634]
Adding DateTime part functions (#3669) - Added `Zone`, `Date_Time` and `Time_Of_Day` to `Standard.Base`. - Renamed `Zone` to `Time_Zone`. - Added `century`. - Added `is_leap_year`. - Added `length_of_year`. - Added `length_of_month`. - Added `quarter`. - Added `day_of_year`. - Added `Day_Of_Week` type and `day_of_week` function. - Updated `week_of_year` to support ISO. # Important Notes - Had to pass locale to formatter for date/time tests to work on my PC. - Changed default of `week_of_year` to use ISO.
2022-08-26 18:47:58 +03:00
- [Added various date part functions to `Date` and `Date_Time`.][3669]
Add `Table.take` and `Table.drop` functions to In-Memory table (#3647) Implements https://www.pivotaltracker.com/story/show/182307347
2022-08-26 22:41:36 +03:00
- [Implemented `Table.take` and `Table.drop` for the in-memory backend.][3647]
Add storage support for Date, Time and DateTime to InMemory table (#3673) Implements https://www.pivotaltracker.com/story/show/183080911
2022-09-01 01:06:29 +03:00
- [Implemented specialized storage for the in-memory Table.][3673]
Add `Table.distinct` function to In-Memory table (#3684) Implements https://www.pivotaltracker.com/story/show/182307143 # Important Notes - Modified standard library Java helpers dependencies so that `std-table` module depends on `std-base`, as a provided dependency. This is allowed, because `std-table` is used by the `Standard.Table` Enso module which depends on `Standard.Base` which ensures that the `std-base` is loaded onto the classpath, thus whenever `std-table` is loaded by `Standard.Table`, so is `std-base`. Thus we can rely on classes from `std-base` and its dependencies being _provided_ on the classpath. Thanks to that we can use utilities like `Text_Utils` also in `std-table`, avoiding code duplication. Additional advantage of that is that we don't need to specify ICU4J as a separate dependency for `std-table`, since it is 'taken' from `std-base` already - so we avoid including it in our build packages twice.
2022-09-07 15:28:41 +03:00
- [Implemented `Table.distinct` for the in-memory backend.][3684]
Restructuring `Database.Connection` to allow for database specific types. (#3632) - Added `databases`, `database`, `set_database`. - Added `schemas`, `schema`, `set_schema`. - Added `table_types`, - Added `tables`. - Moved the vast majority of the connection work into a lower level `JDBC_Connection` object. - `Connection` represents the standard API for database connections and provides a base JDBC implementation. - `SQLite_Connection` has the `Connection` API but with custom `databases` and `schemas` methods for SQLite. - `Postgres_Connection` has the `Connection` API but with custom `set_database`, `databases`, `set_schema` and `schemas` methods for Postgres. - Updated `Redshift` - no public API change.
2022-09-07 20:32:28 +03:00
- [Added `databases`, `schemas`, `tables` support to database Connection.][3632]
Add Period Start and End functions to Date and DateTime (#3695) Implements https://www.pivotaltracker.com/story/show/183081152
2022-09-13 12:51:08 +03:00
- [Implemented `start_of` and `end_of` methods for date/time types allowing to
find start and end of a period of time containing the provided time.][3695]
Implement `type_of` (#3722) This change implements a simple `type_of` method that returns a type of a given value, including for polyglot objects. The change also allows for pattern matching on various time-related instances. It is a nice-to-have on its own, but it was primarily needed here to write some tests. For equality checks on types we currently can't use `==` due to a known _feature_ which essentially does wrong dispatching. This will be improved in the upcoming statics PR so we agreed that there is no point in duplicating that work and we can replace it later. Also, note that this PR changes `Meta.is_same_object`. Comparing types revealed that it was wrong when comparing polyglot wrappers over the same value.
2022-09-26 19:01:39 +03:00
- [Implemented `type_of` and `is_of_type` methods for getting the type of a
value and comparing types, respectively.][3722]
Add business days functions to Date and Date_Time (#3726) Implements https://www.pivotaltracker.com/story/show/183082087 # Important Notes - Removed unnecessary invocations of `Error.throw` improving performance of `Vector.distinct`. The time of the `add_work_days and work_days_until should be consistent with each other` test suite came down from 15s to 3s after the changes.
2022-09-22 11:31:15 +03:00
- [Implemented `work_days_until` for counting work dys between dates and
`add_work_days` which allows to shift a date by a number of work days.][3726]
Adjust Database connection to use query/read to access data. (#3727) Adjust Database connection API to align with new [design](https://github.com/enso-org/design/blob/wip/jd/database-read/epics/basic-libraries/database-read/design.md#querying-tables). - `query` replaces the old `access_table` and is expanded to support raw SQL queries. - `read` replaces `execute_query` and matches the API of `query`. - `to_dataframe` is renamed to `read`. # Important Notes Added support for `++` to concatenate a Text without wrapping in a `SQL.Code`.
2022-09-23 10:35:08 +03:00
- [Added `query` and `read` functions to Database connections.][3727]
Add `Date_Period.Week` to `start_of` and `end_of` methods (#3733) Implements https://www.pivotaltracker.com/story/show/183349732
2022-09-24 01:14:35 +03:00
- [Added `Date_Period.Week` to `start_of` and `end_of` methods.][3733]
Update Table API with new `filter` design (#3750) Implements https://www.pivotaltracker.com/story/show/183389855 # Important Notes Implements basic filter operations both In-Memory and for the Database backend, ensuring that existing tests can be adapted and keep working. Not all `Filter_Condition`s are implemented yet. Also implements significant part of https://www.pivotaltracker.com/story/show/183390314
2022-10-05 14:40:10 +03:00
- [Replaced `Table.where` with a new API relying on `Table.filter`.][3750]
Add filtering by Filter_Condition to `Vector`, `Range` and `List` (#3770) Implements https://www.pivotaltracker.com/story/show/183389901
2022-10-07 07:02:54 +03:00
- [Added `Filter_Condition` to `Vector`, `Range` and `List`.][3770]
Add `Is_Empty`, `Not_Empty`, `Like` and `Not_Like` to `Filter_Condition` (#3775) Implements https://www.pivotaltracker.com/story/show/183389890
2022-10-11 02:11:04 +03:00
- [Extended `Filter_Condition` with `Is_Empty`, `Not_Empty`, `Like` and
`Not_Like`.][3775]
Duration type is a builtin type (#3759) - Reimplement the `Duration` type to a built-in type. - `Duration` is an interop type. - Allow Enso method dispatch on `Duration` interop coming from different languages. # Important Notes - The older `Duration` type should now be split into new `Duration` builtin type and a `Period` type. - This PR does not implement `Period` type, so all the `Period`-related functionality is currently not working, e.g., `Date - Period`. - This PR removes `Integer.milliseconds`, `Integer.seconds`, ..., `Integer.years` extension methods.
2022-10-14 21:08:08 +03:00
- [Reimplemented `Duration` as a built-in type.][3759]
Add `replace_text` method to In-Memory `Table` (#3793) Implements https://www.pivotaltracker.com/n/projects/2539304/stories/183415329
2022-10-14 18:42:29 +03:00
- [Implemented `Table.replace_text` for in-memory table.][3793]
Add support for `Is_In` and `Not_In` to `Filter_Condition` (#3790) Implements https://www.pivotaltracker.com/story/show/183389945
2022-10-15 14:29:59 +03:00
- [Extended `Filter_Condition` with `Is_In` and `Not_In`.][3790]
Update `drop_missing_rows` to `filter_blank_rows` API. (#3805) Implements https://www.pivotaltracker.com/story/show/183390042 and https://www.pivotaltracker.com/story/show/183390370
2022-10-18 18:58:50 +03:00
- [Replaced `Table.drop_missing_rows` with `filter_blank_rows` with an updated
API.][3805]
Add support for `Blank_Columns` to Table and Database (#3812) Implements https://www.pivotaltracker.com/story/show/183390281 and https://www.pivotaltracker.com/story/show/183390394
2022-10-20 12:11:08 +03:00
- [Replaced `Table.drop_missing_columns` with
`Table.remove_columns Column_Selector.Blank_Columns` by adding the new column
selector variant.][3812]
Create a Table `Row` Type and expose as a Vector on In-Memory Table with `.rows` property (#3827) Implements https://www.pivotaltracker.com/story/show/182307026
2022-10-26 14:21:33 +03:00
- [Implemented `Table.rows` giving access to a vector of rows.][3827]
Define Enso epoch start as 15th October 1582. (#3804) Define start of Enso epoch as 15th of October 1582 - start of the Gregorian calendar. # Important Notes - Some (Gregorian) calendar related functionalities within `Date` and `Date_Time` now produces a warning if the receiving Date/Date_Time is before the epoch start, e.g., `week_of_year`, `is_leap_year`, etc.
2022-10-27 13:16:43 +03:00
- [Define Enso epoch start as 15th October 1582][3804]
Add `Period` type (#3818) This PR adds `Period` type, which is a date-only complement to `Duration` builtin type. # Important Notes - `Period` replaces `Date_Period`, and `Time_Period`. - Added shorthand constructors for `Duration` and `Period`. For example: `Period.days 10` instead of `Period.new days=10`. - `Period` can be compared to other `Period` in some cases, other cases throw an error.
2022-10-28 20:27:20 +03:00
- [Implemented `Period` type][3818]
Expanding Derived Columns and Expression Syntax (#3782) - Added expression ANTLR4 grammar and sbt based build. - Added expression support to `set` and `filter` on the Database and InMemory `Table`. - Added expression support to `aggregate` on the Database and InMemory `Table`. - Removed old aggregate functions (`sum`, `max`, `min` and `mean`) from `Column` types. - Adjusted database `Column` `+` operator to do concatenation (`||`) when text types. - Added power operator `^` to both `Column` types. - Adjust `iif` to allow for columns to be passed for `when_true` and `when_false` parameters. - Added `is_present` to database `Column` type. - Added `coalesce`, `min` and `max` functions to both `Column` types performing row based operation. - Added support for `Date`, `Time_Of_Day` and `Date_Time` constants in database. - Added `read` method to InMemory `Column` returning `self` (or a slice). # Important Notes - Moved approximate type computation to `SQL_Type`. - Fixed issue in `LongNumericOp` where it was always casting to a double. - Removed `head` from InMemory Table (still has `first` method).
2022-11-08 18:57:59 +03:00
- [Implemented new functions on Column and added expression syntax support to
create derived Columns.][3782]
Some minor fixes (#3874) - Allow `Map` to store a `Nothing` key (fixes `Vector.distinct` with a `Nothing`). - Add `column_names` method to `Table` as a shorthand. - Return data flow error when comparing with Nothing (not a Panic or a Polyglot exception). - Allow milli and micro second for DateTime and Time Of Day # Important Notes - Added a load of tests for the various comparison operators to Numbers_Spec.
2022-11-17 10:11:18 +03:00
- [Added support for milli and micro seconds, new short form for rename_columns
and fixed issue with compare_to versus Nothing][3874]
Data analysts should be able to `Text.match`, `Text.match_all`, `Text.is_match` to find or check matches (#3841) Implements https://www.pivotaltracker.com/story/show/181266092 # Important Notes Also renaming `Text.location_of` and `Text.location_of_all` to `Text.locate` and `Text.locate_all`.
2022-11-19 01:17:42 +03:00
- [Aligned `Text.match`/`Text.locate` API][3841]
Implement Lazy Text Visualisation. (#3910) Implements [#183453466](https://www.pivotaltracker.com/story/show/183453466). https://user-images.githubusercontent.com/1428930/203870063-dd9c3941-ce79-4ce9-a772-a2014e900b20.mp4 # Important Notes * the best laziness is used for `Text` type, which makes use of its internal representation to send data * any type will first compute its default string representation and then send the content of that lazy to the IDE * special handling of files and their content will be implemented in the future * size of the displayed text can be updated dynamically based on best effort information: if the backend does not yet know the full width/height of the text, it can update the IDE at any time and this will be handled gracefully by updating the scrollbar position and sizes.
2023-01-24 23:55:36 +03:00
- [There is a new API to lazily feed visualisation information to the
IDE.][3910]
Implementing transpose and cross_tab for the InMemory table. (#3919) - Adds transpose and cross_tab to the In-Memory table. - Cross Tab is built on top of aggregate and hence allows for expressions and has same error trapping as in aggregate. # Important Notes Only basic tests have been implemented. Error and warning tests will be added as a follow up task.
2022-11-30 04:19:25 +03:00
- [Added `transpose` and `cross_tab` to the In-Memory Table.][3919]
JSON Improvements, small Table stuff, Statistic in Enso not Java and few other minor bits. (#3964) - Aligned `compare_to` so returns `Type_Error` if `that` is wrong type for `Text`, `Ordering` and `Duration`. - Add `empty_object`, `empty_array`. `get_or_else`, `at`, `field_names` and `length` to `Json`. - Fix `Json` serialisation of NaN and Infinity (to "null"). - Added `length`, `at` and `to_vector` to Pair (allowing it to be treated as a Vector). - Added `running_fold` to the `Vector` and `Range`. - Added `first` and `last` to the `Vector.Builder`. - Allow `order_by` to take a single `Sort_Column` or have a mix of `Text` and `Sort_Column.Name` in a `Vector`. - Allow `select_columns_helper` to take a `Text` value. Allows for a single field in group_by in cross_tab. - Added `Patch` and `Custom` to HTTP_Method. - Added running `Statistic` calculation and moved more of the logic from Java to Enso. Performance seems similar to pure Java version now.
2022-12-14 22:40:27 +03:00
- [Improvements to JSON, Pair, Statistics and other minor tweaks.][3964]
Let JavaScript parse JSON and write JSON ... (#3987) Use JavaScript to parse and serialise to JSON. Parses to native Enso object. - `.to_json` now returns a `Text` of the JSON. - Json methods now `parse`, `stringify` and `from_pairs`. - New `JSON_Object` representing a JavaScript Object. - `.to_js_object` allows for types to custom serialize. Returning a `JS_Object`. - Default JSON format for Atom now has a `type` and `constructor` property (or method to call for as needed to deserialise). - Removed `.into` support for now. - Added JSON File Format and SPI to allow `Data.read` to work. - Added `Data.fetch` API for easy Web download. - Default visualization for JS Object trunctes, and made Vector default truncate children too. Fixes defect where types with no constructor crashed on `to_json` (e.g. `Matching_Mode.Last.to_json`. Adjusted default visualisation for Vector, so it doesn't serialise an array of arrays forever. Likewise, JS_Object default visualisation is truncated to a small subset. New convention: - `.get` returns `Nothing` if a key or index is not present. Takes an `other` argument allowing control of default. - `.at` error if key or index is not present. - `Nothing` gains a `get` method allowing for easy propagation.
2022-12-20 13:33:46 +03:00
- [Overhauled the JSON support (now based of JavaScript), `Data.fetch` and other
minor tweaks][3987]
Adds Date, Time_Of_Day and Date_Time support to Excel IO (#3997) - Allow date time inputs from Excel. - Enables disabled test. - Fix for Map.==. - Allow nulls in crosstab name.
2022-12-20 19:12:00 +03:00
- [Enable Date, Time and DateTime to be read and written to Excel.][3997]
Align Vector API with design, add some extra functions from AoC (#4026) **Vector** - Adjusted `Vector.sort` to be `Vector.sort order on by`. - Adjusted other sort to use `order` for direction argument. - Added `insert`, `remove`, `index_of` and `last_index_of` to `Vector`. - Added `start` and `if_missing` arguments to `find` on `Vector`, and adjusted default is `Not_Found` error. - Added type checking to `+` on `Vector`. - Altered `first`, `second` and `last` to error with `Index_Out_Of_Bounds` on `Vector`. - Removed `sum`, `exists`, `head`, `init`, `tail`, `rest`, `append`, `prepend` from `Vector`. **Pair** - Added `last`, `any`, `all`, `contains`, `find`, `index_of`, `last_index_of`, `reverse`, `each`, `fold` and `reduce` to `Pair`. - Added `get` to `Pair`. **Range** - Added `first`, `second`, `index_of`, `last_index_of`, `reverse` and `reduce` to `Range`. - Added `at` and `get` to `Range`. - Added `start` and `if_missing` arguments to `find` on `Range`. - Simplified `last` and `length` of `Range`. - Removed `exists` from `Range`. **List** - Added `second`, `find`, `index_of`, `last_index_of`, `reverse` and `reduce` to `Range`. - Added `at` and `get` to `List`. - Removed `exists` from `List`. - Made `all` short-circuit if any fail on `List`. - Altered `is_empty` to not compute the length of `List`. - Altered `first`, `tail`, `head`, `init` and `last` to error with `Index_Out_Of_Bounds` on `List`. **Others** - Added `first`, `second`, `last`, `get` to `Text`. - Added wrapper methods to the Random_Number_Generator so you can get random values more easily. - Adjusted `Aggregate_Column` to operate on the first column by default. - Added `contains_key` to `Map`. - Added ALIAS to `row_count` and `order_by`.
2023-01-12 16:32:24 +03:00
- [Aligning core APIs for Vector, List and Range. Adding some missing functions
to the types.][4026]
Implement Distinct for the Database backends (#4027) Implements https://www.pivotaltracker.com/story/show/182307281
2023-01-12 01:46:54 +03:00
- [Implemented `Table.distinct` for Database backends.][4027]
Add `Table.union` to the In-Memory Table. (#4052) Implements https://www.pivotaltracker.com/story/show/183854144
2023-01-17 03:34:57 +03:00
- [Implemented `Table.union` for the in-memory backend.][4052]
Add Table.cross_join and Table.zip to In-Memory Table (#4063) Implements https://www.pivotaltracker.com/story/show/184239059
2023-01-23 16:19:52 +03:00
- [Implemented `Table.cross_join` and `Table.zip` for the in-memory
backend.][4063]
Update starts_with, ends_with and contains to new API design (#4078) - Updated `Text.starts_with`, `Text.ends_with` and `Text.contains` to new simpler API. - Added a `Case_Sensitivity.Default` and adjusted `Table.distinct` to use it by default. - Fixed a bug with `Data.fetch` on an HTTP error. - Improved SQLite Case Sensitivity control in distinct to use collations.
2023-01-25 14:47:27 +03:00
- [Updated `Text.starts_with`, `Text.ends_with` and `Text.contains` to new
simpler API.][4078]
New set function, parse a column (#4097) - New `set` function design - takes a `Column` and works with that more easily and supports control of `Set_Mode`. - New simple `parse` API on `Column`. - Separated expression support for `filter` to new `filter_by_expression` on `Table`. - New `compute` function allowing creation of a column from an expression. - Added case sensitivity argument to `Column` based on `starts_with`, `ends_with` and `contains`. - Added case sensitivity argument to `Filter_Condition` for `Starts_With`, `Ends_With`, `Contains` and `Not_Contains`. - Fixed the issue in JS Table visualisation where JavaScript date was incorrectly set. - Some dynamic dropdown expressions - experimenting with ways to use them. - Fixed issue with `.pretty` that wasn't escaping `\`. - Changed default Postgres DB to `postgres`. - Fixed SQLite support for starts_with, ends_with and contains to be consistent (using GLOB not LIKE).
2023-01-31 23:48:16 +03:00
- [Updated `Table.set` to new API. New `Column.parse` function and added case
sensitivity to `Filter_Condition` and column functions.][4097]
Remove `Column` type from Aggregate_Column, simplify Column_Selector, some new `File_Format`s (#5646) - Updated `Widget.Vector_Editor` ready for use by IDE team. - Added `get` to `Row` to make API more aligned. - Added `first_column`, `second_column` and `last_column` to `Table` APIs. - Adjusted `Column_Selector` and associated methods to have simpler API. - Removed `Column` from `Aggregate_Column` constructors. - Added new `Excel_Workbook` type and added to `Excel_Section`. - Added new `SQLiteFormatSPI` and `SQLite_Format`. - Added new `IamgeFormatSPI` and `Image_Format`.
2023-02-16 18:15:49 +03:00
- [Updated column selector APIs and new `Excel_Workbook` type.][5646]
Update Text.locate, Text.locate_all, Text.index_of and Text.last_index_of #5119 (#5679) Remove regex support from .locate and .locate_all; regex functionality is moved to .match and .match_all where appropriate. This is in preparation for simplifying regex support across the board. Also change Matching_Mode types to a single type with two variants. Note: the matcher parameter to .locate and .locate_all has been replaced by a case_sensitivity parameter, of type Case_Sensitivity, which differs in that it also has a Default option. Default is treated as Sensitive.
2023-02-17 22:41:55 +03:00
- [Moved regex functionality out of `Text.locate` and `Text.locate_all` into
`Text.match` and `Text.match_all`.][5679]
File.parent can return Nothing (#5699) `File.parent` can be `Nothing`
2023-02-20 22:13:56 +03:00
- [`File.parent` may return `Nothing`.][5699]
Wip/gmt/match find only text (#5721) Rename is_match + match to match + find (respectively), and remove all non-regexp functionality. Regexp flags and Match_Mode are also no longer supported by these methods.
2023-02-23 12:47:10 +03:00
- [Removed non-regex functionality from `is_match`, `match`, and `match_all`,
and renamed them to `match`, `find`, `find_all` (respectively).][5721]
Update `rename_columns` to new API design, add `first_row`, `second_row` and `last_row` functions to the table. (#5719) - Updates the `rename_columns` API. - Add `first_row`, `second_row` and `last_row` to the Table types. - New option for reading only last row of ResultSet.
2023-02-23 22:42:45 +03:00
- [Updated `rename_columns` to new API. Added `first_row`, `second_row` and
`last_row` to Table types][5719]
Introducing Meta.Type (#5956) Fixing #5768 and #5765 and co. Introducing `Meta.Type` and giving it the desired methods. # Important Notes `Type` is no longer a `Meta.Atom`, but it has a dedicated `Meta.Type` representation.
2023-03-17 23:08:18 +03:00
- [Introducing `Meta.Type`.][5768]
Regex.Compile using Truffle Regex, update find, match and match_all (#5785)
2023-03-11 00:49:50 +03:00
- [Remove many regex compile flags; separated `match` into `match` and
`match_all`.][5785]
Review generated Column names (#5850) Closes #5583 and closes #5157
2023-03-10 22:07:58 +03:00
- [Aligned names of columns created by column operations.][5850]
Fix `cross_tab` column naming edge cases, add `fill_empty` (#5863) Closes #5151 and adds some additional tests for `cross_tab` that verify duplicated and invalid names. I decided that for empty or `Nothing` names, instead of replacing them with `Column` and implicitly losing connection with the value that was in the column, we should just error on such values. To make handling of these easier, `fill_empty` was added allowing to easily replace the empty values with something else. Also, `{is,fill}_missing` was renamed to `{is,fill}_nothing` to align with `Filter_Condition.Is_Nothing`.
2023-03-11 14:58:54 +03:00
- [Improved `cross_tab`. Renamed `fill_missing` and `is_missing` to
`fill_nothing` and `is_nothing`. Added `fill_empty`.][5863]
Implement Regular Expression split and update Text.split to the new API (#6116) Re-implement split on top of Truffle regex.
2023-03-30 16:05:30 +03:00
- [Removed many regex compile flags from `replace`; added `only_first` and
`use_regex` flag.][5959]
#5123 Text.tokenize (#6150) Implement Text.tokenize.
2023-04-03 23:13:49 +03:00
- [Implemented proper support for Value Types in the Table library.][6073]
Implement Regular Expression split and update Text.split to the new API (#6116) Re-implement split on top of Truffle regex.
2023-03-30 16:05:30 +03:00
- [Removed many regex compile flags from `split`; added `only_first` and
`use_regex` flag.][6116]
#5123 Text.tokenize (#6150) Implement Text.tokenize.
2023-04-03 23:13:49 +03:00
- [Added `Text.tokenize`][6150]
Date/time support for Postgres. Year/month/day operations on Columns. (#6153) Closes #6115
2023-03-31 21:37:04 +03:00
- [Added support for Date/Time columns in the Postgres backend and added
`year`/`month`/`day` operations to Table columns.][6153]
Update `Text.split` to take a `Vector Text` parameter (#6156) Allows you to pass a vector of delimiters to `split`.
2023-04-04 17:44:47 +03:00
- [`Text.split` can now take a vector of delimiters.][6156]
Add Warning methods onto Any to make working with them easier. (#6176) Adds `has_warnings`, `remove_warnings` and `throw_on_warning` extension methods.
2023-04-12 18:08:01 +03:00
- [Add `has_warnings`, `remove_warnings` and `throw_on_warning` extension
methods.][6176]
Implement `Table.union` for Database backend (#6204) Closes #5235
2023-04-06 11:40:34 +03:00
- [Implemented `Table.union` for the Database backend.][6204]
Consolidate Vector and Array methods (#6218) Fixes #5011 by making sure the same methods that are on `Vector` are also available on `Array`.
2023-04-11 19:20:11 +03:00
- [Array & Vector have the same methods & behavior][6218]
Add split and tokenize to the Table. (#6233) Implement split and tokenize for tables.
2023-04-14 19:03:02 +03:00
- [Implemented `Table.split` and `Table.tokenize` for in-memory tables.][6233]
Add `replace`, `trim` to Column. Better number parsing. (#6253) - Add `replace` with same syntax as on `Text` to an in-memory `Column`. - Add `trim` with same syntax as on `Text` to an in-memory `Column`. - Add `trim` to in-database `Column`. - Added `is_supported` to dialects and exposed the dialect consistently on the `Connection`. - Add `write_table` support to `JSON_File` allowing `Table.write` to write JSON. - Updated the parsing for integers and decimals: - Support for currency symbols. - Support for brackets for negative numbers. - Automatic detection of decimal points and thousand separators. - Tighter rules for scientific and thousand separated numbers. - Remove `replace_text` from `Table`. - Remove `write_json` from `Table`.
2023-04-20 19:04:59 +03:00
- [Added `trim` and `replace` to `Column`. Enhanced number parsing with support
for thousands and decimal point automatic detection.][6253]
Add Table.parse_text_to_table to convert Text to a Table. (#6294)
2023-04-21 20:43:19 +03:00
- [Implemented `Table.parse_text_to_table`.][6294]
5127 Add Table.parse_to_columns to parse a single column to a set of columns. (#6383) Implement Table.parse_to_columns
2023-04-24 18:21:38 +03:00
- [Added `Table.parse_to_columns`.][6383]
Add parse extensions to Text type. #6330 (#6404) Add type-specific parse stubs to Text, e.g.: Text.parse_json self -> Json = Text.parse_url self -> Url = Text.parse_number self -> Number =
2023-04-26 18:37:09 +03:00
- [Added parsing methods for `Integer`, `Decimal`, `Json`, `Date`, `Date_Time`,
`Time_Of_Day`, `Time_Zone`, and `URI` to `Text`.][6404]
Create database table from memory (#6429)
2023-04-27 23:06:17 +03:00
- [Implemented `create_database_table` allowing upload of in-memory
tables.][6429]
Add Execution Context control to Text.write (#6459) - Adjusted `Context.is_enabled` to support default argument (moved built in so can have defaults). - Made `environment` case-insensitive. - Bug fix for play button. - Short hand to execute within an enabled context. - Forbid file writing if the Output context is disabled with a `Forbidden_Operation` error. - Add temporary file support via `File.create_temporary_file` which is deleted on exit of JVM. - Execution Context first pass in `Text.write`. - Added dry run warning. - Writes to a temporary file if disabled. - Created a `DryRunFileManager` which will create and manage the temporary files. - Added `format` dropdown to `File.read` and `Data.read`. - Renamed `JSON_File` to `JSON_Format` to be consistent. (still to unit test).
2023-04-29 11:39:18 +03:00
- [Added execution context control to writing files and dry run capabilities to
`Text.write`.][6459]
Implement `create_database_table` for Database Table (#6467) Closes #6327
2023-05-02 17:01:44 +03:00
- [Implemented `create_database_table` allowing saving queries as database
tables.][6467]
Add format to the in-memory Column (#6538) Add format to the in-memory Column # Important Notes Also updates .format in date types. Some rearrangement of date formatting builtins / Java libraries.
2023-05-09 11:47:40 +03:00
- [Implemented `Column.format` for in-memory `Column`s.][6538]
"at_least_one" flag for tokenize_to_rows (#6539) Add "at_least_one" flag for tokenize_to_rows.
2023-05-06 09:22:09 +03:00
- [Added `at_least_one` flag to `Table.tokenize_to_rows`.][6539]
Separating Redshift connector from `Database` library into a new `AWS` library (#6550) Related to #5777
2023-05-04 20:36:51 +03:00
- [Moved `Redshift` connector into a separate `AWS` library.][6550]
Add `Date_Range` (#6621) Closes #6543
2023-05-11 19:03:02 +03:00
- [Added `Date_Range`.][6621]
Implement `cast` for Table and Column (#6711) Closes #6112
2023-05-19 13:00:20 +03:00
- [Implemented the `cast` operation for `Table` and `Column`.][6711]
Decimal/Integer .round and .int #6654 (#6743)
2023-05-19 22:23:17 +03:00
- [Added `.round` and `.int` to `Integer` and `Decimal`.][6743]
Add rounding functions to the Column type (#6817)
2023-06-01 23:06:23 +03:00
- [Added `.round`, `.truncate`, `.ceil`, and `.floor` to `Column`.][6817]
Execution control for Table.write and various widget tweaks... (#6835) - Adds execution control to `Table.write`. - Refactored the `Text.write` to make part reusable. - Tidied up some legacy mess in tests. - Add easier flow to go from `Text` to an `URI` to fetching data. - Add decode functions to `Response` and `Response_Body`. - Fix issue with 0 length regex matches (using same as Python and .Net approach). - Add various ALIAS entries to make function discovery easier. - Sort a lot of drop down and vector editors out (including switch to fully qualified names).
2023-06-02 01:10:03 +03:00
- [Added execution control to `Table.write` and various bug fixes.][6835]
Implement `Table.add_row_number` (#6890) Closes #5227 # Important Notes - This lays first steps towards #6292 - we get pure Enso variants of MultiValueKey. - Another part refactors `LongStorage` into `AbstractLongStorage` allowing it to provide alternative implementations of the underlying storage, in our case `LongRangeStorage` generating the values ad-hoc and `LongConstantStorage` - currently unused but in the future it can be adapted to support constant columns (once we implement similar facilities for other types).
2023-06-02 13:13:13 +03:00
- [Implemented `Table.add_row_number`.][6890]
Handle some edge cases in rounding (inexact representations and overflows) (#6922)
2023-06-05 20:21:13 +03:00
- [Handling edge cases in rounding.][6922]
Refactor `create_database_table` into `Connection.create_table` and `select_into_database_table`, implement `Set`. (#6925) First part for #6498 - refactoring of the upload infrastructure, in preparation for `update_database_table`. Implemented a `Set` data structure which was long needed. The APIs are added and an initial implementation is created, but it is not complete - but it has grown significantly already so the remaining implementation will be done as a separate PR. Adds some basic ability for a function to ensure that it is only executed from within a transaction.
2023-06-06 13:36:05 +03:00
- [Split `Table.create_database_table` into `Connection.create_table` and
`Table.select_into_database_table`.][6925]
Reimplement Column.truncate, .ceil, and .floor as vectorized Java ops (#6941) Reimplement these in Java. Benchmarks: Before: Column.truncate floats average: 124.4ms Column.ceil floats average: 121.47ms Column.floor floats average: 120.18ms Column.truncate ints average: 124.78ms Column.ceil ints average: 120.41ms Column.floor ints average: 102.35ms After (boxed): Column.truncate floats average: 3.75ms Column.ceil floats average: 2.25ms Column.floor floats average: 1.89ms Column.truncate ints average: 2ms Column.ceil ints average: 1.77ms Column.floor ints average: 1.74ms After (unboxed): Column.truncate floats average: 3.32ms Column.ceil floats average: 2.15ms Column.floor floats average: 1.69ms Column.truncate ints average: 1.74ms Column.ceil ints average: 1.61ms Column.floor ints average: 1.99ms
2023-06-06 21:07:12 +03:00
- [Speed improvements to `Column` `.truncate`, `.ceil`, and `.floor`.][6941]
Implement addition and subtraction for Date_Period and Time_Period (#6956) Date.+ should allow Date_Period, Time_Of_Day.+ should allow Time_Period and Date_TIme.+ should allow both. Same for subtraction.
2023-06-07 15:46:19 +03:00
- [Implemented addition and subtraction for `Date_Period` and
`Time_Period`.][6956]
Implement remaining `Update_Action`s for `update_database_table`. (#7035) Closes #6498
2023-06-15 11:48:22 +03:00
- [Implemented `Table.update_database_table`.][7035]
First part of AWS S3 API, various small fixes. (#6973) - Add type detection for `Mixed` columns when calling column functions. - Excel uses column name for missing headers. - Add aliases for parse functions on text. - Adjust `Date`, `Time_Of_Day` and `Date_Time` parse functions to not take `Nothing` anymore and provide dropdowns. - Removed built-in parses. - All support Locale. - Add support for missing day or year for parsing a Date. - All will trim values automatically. - Added ability to list AWS profiles. - Added ability to list S3 buckets. - Workaround for Table.aggregate so default item added works.
2023-06-15 19:20:13 +03:00
- [Added AWS credential support and initial S3 list buckets API.][6973]
Improving widgets and other minor tweaks. (#7052) - Removed `module` argument from `enso_project` (new `Project_Description.new` API). - Removed the custom option from date and time parse/format dropdowns. - The `format` dropdown uses the value to create the dropdown. (Screenshot below) - Removed `StorageType` coalescing rules and replaced them with simpler logic in `ObjectStorage`. - Update signature for `add_row_number` and add aliases.
2023-06-19 22:03:36 +03:00
- [Removed `module` argument from `enso_project` and other minor tweaks.][7052]
The user should be able to remove duplicate elements from a Vector (#3224)
2022-01-17 12:51:56 +03:00
Debug Mode for Graph Editor (#3264)
2022-02-14 13:19:08 +03:00
[debug-shortcuts]:
https://github.com/enso-org/enso/blob/develop/app/gui/docs/product/shortcuts.md#debug
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
[3153]: https://github.com/enso-org/enso/pull/3153
Lazy scatterplot for Vector & Table (#3655) First of all this PR demonstrates how to implement _lazy visualization_: - one needs to write/enhance Enso visualization libraries - this PR adds two optional parameters (`bounds` and `limit`) to `process_to_json_text` function. - the `process_to_json_text` can be tested by standard Enso test harness which this PR also does - then one has to modify JavaScript on the IDE side to construct `setPreprocessor` expression using the optional parameters The idea of _scatter plot lazy visualization_ is to limit the amount of points the IDE requests. Initially the limit is set to `limit=1024`. The `Scatter_Plot.enso` then processes the data and selects/generates the `limit` subset. Right now it includes `min`, `max` in both `x`, `y` axis plus randomly chosen points up to the `limit`. ![Zooming In](https://user-images.githubusercontent.com/26887752/185336126-f4fbd914-7fd8-4f0b-8377-178095401f46.png) The D3 visualization widget is capable of _zooming in_. When that happens the JavaScript widget composes new expression with `bounds` set to the newly visible area. By calling `setPreprocessor` the engine recomputes the visualization data, filters out any data outside of the `bounds` and selects another `limit` points from the new data. The IDE visualization then updates itself to display these more detailed data. Users can zoom-in to see the smallest detail where the number of points gets bellow `limit` or they can select _Fit all_ to see all the data without any `bounds`. # Important Notes Randomly selecting `limit` samples from the dataset may be misleading. Probably implementing _k-means clustering_ (where `k=limit`) would generate more representative approximation.
2022-08-23 15:12:22 +03:00
[3655]: https://github.com/enso-org/enso/pull/3655
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
[3166]: https://github.com/enso-org/enso/pull/3166
Register Views before creating them (#3181)
2021-12-08 10:11:58 +03:00
[3181]: https://github.com/enso-org/enso/pull/3181
Fix some edits not being sent to LangServ (#3186) Some edits were not being sent by IDE to Language Server, resulting in 3003 "Invalid version" errors being returned by LangServ, and forcing full invalidation (resynchronization) of text contents in LangServ. This change fixes such errors observed when opening a new project, creating a new project, or adding a new node to a project. Fixes #3094 ### Important Notes The root cause showed up to be actually two separate issues, both of them reproduced by an "opening a new project" scenario: 1. The automatic addition of `import Standard.Visualization` line, [done internally when opening a new project in `controller::Project::initialize()`](https://github.com/enso-org/enso/blob/c14a2d81698217349394597fea778fd86bba47df/app/gui/src/controller/project.rs#L137-L141), was not reaching the Language Server. The cause of it was a race condition with [`self.model.subscribe()` in `Module::runner()`](https://github.com/enso-org/enso/blob/c14a2d81698217349394597fea778fd86bba47df/app/gui/src/model/module/synchronized.rs#L268). In particular, the addition of the import was executed before the subscription, which resulted in an edition notification being lost and not sent to LangServer. The fix employed for this is to make the `subscribe()` call synchronous during the initialization of a project, instead of scheduling it for a non-deterministic later time. 2. There was [a bug in `synchronized::Module::edit_for_snipped()`](https://github.com/enso-org/enso/blob/7467efda592ab5d7ce29122af20020293f9ceacf/app/gui/src/model/module/synchronized.rs#L362), making it erroneously "optimize out" any code insertions detected by `TextEdit::from_prefix_postfix_differences()`. The fix employed for this was to improve the "optimizing out" condition, together with adding an accompanying test case verifying correct behavior (protecting against a future regression). Additionally, as a drive-by improvement, some statements in `ParsedSourceFile<>::serialize()` were reordered, to make them better match how the actual contents of an .enso file are structured, and thus make it easier to read/analyze the code.
2021-12-13 20:18:20 +03:00
[3186]: https://github.com/enso-org/enso/pull/3186
Fix problems related to error visualisation evaluation (#3193) - Add parser & handler in IDE for `executionContext/visualisationEvaluationFailed` message from Engine (fixes a developer console error "Failed to decode a notification: unknown variant `executionContext/visualisationEvaluationFailed`"). The contents of the error message will now be properly deserialized and printed to Dev Console with appropriate details. - Fix a bug in an Enso code snippet used internally by the IDE for error visualizations preprocessing. The snippet was using not currently supported double-quote escaping in double-quote delimited strings. This lack of processing is actually a bug in the Engine, and it was reported to the Engine team, but changing the strings to single-quoted makes the snippet also more readable, so it sounds like a win anyway. - A test is also added to the Engine CI, verifying that the snippet compiles & works correctly, to protect against similar regressions in the future. Related: #2815
2021-12-21 12:00:57 +03:00
[3193]: https://github.com/enso-org/enso/pull/3193
Support source maps for JS-based visualizations (#3208)
2022-01-11 15:31:43 +03:00
[3208]: https://github.com/enso-org/enso/pull/3208
The user should be able to remove duplicate elements from a Vector (#3224)
2022-01-17 12:51:56 +03:00
[3224]: https://github.com/enso-org/enso/pull/3224
Moving distinct to Map (#3229) * Moving distinct to Map * Mixed Type Comparable Wrapper * Missing Bracket Still an issue with `Integer` in the mixed vector test * PR comments * Use naive approach for mixed types * Enable pending test * Performance timing function * Handle incomparable types cleanly * Tidy up the time_execution function * PR comments. * Change log
2022-01-25 12:57:30 +03:00
[3229]: https://github.com/enso-org/enso/pull/3229
Implement creating nodes by dropping a connection (#3231)
2022-01-26 14:23:55 +03:00
[3231]: https://github.com/enso-org/enso/pull/3231
Improve Vector (#3232)
2022-01-25 20:29:39 +03:00
[3232]: https://github.com/enso-org/enso/pull/3232
Data analysts should be able to transform a Table using the select_columns function (#3230) * Utility for mapping errors and warnings * Imlpement By_Index * Expose select_columns in InMem and DB. Need testing * checkpoint: writing tests * Fix minor issues, mock warning mapping for testing purposes * Improve By_Index error handling * A helper for testing problem handling * More error handling * docs * changelog * Fix matching test * Add SQLite tests * cleanup after test * Rework problem handling * small refactor * add examples * Add more test cases for regex matching * Fix Regex.Patter.matches to match full string * "Fix" tests
2022-02-02 12:04:06 +03:00
[3230]: https://github.com/enso-org/enso/pull/3230
Data analysts should be able to transform a Table using the remove_columns and reorder_columns functions (#3240)
2022-02-03 17:18:47 +03:00
[3240]: https://github.com/enso-org/enso/pull/3240
Data analysts should be able to reorder columns into name order using sort_columns functions (#3250)
2022-02-08 19:28:46 +03:00
[3250]: https://github.com/enso-org/enso/pull/3250
Fix vector sorting with TCO comparators (#3256)
2022-02-10 00:17:43 +03:00
[3256]: https://github.com/enso-org/enso/pull/3256
Data analysts should be able to transform a Table using the rename_columns functions (#3249) * Implement Natural_Order and sort_columns * Starting on Rename Align Column_Mapping Add By_Position Separating off the validation for By_Index so can reuse for rename By_Position implemented By_Index implemented Adjusted behaviour following discussion with Ned, so that renames dominate untouched columns. Moving to validation style checks for problems Putting accumulator back Rename work * Add Range.find * More work * Regex support Tidy of Unique Name Strategy * Fix Regex support * Warning messages Tests for Unique Naming Strategy Table rename working * Database Table rename_columns Fix for Table **Must follow up on slice** * Some tests * More tests * Complete test set (and associated fixes) * Functional use_first_row_as_names Tests to go... * Test for use_first_row_as_names * Change log * trailing space Co-authored-by: Radosław Waśko <radoslaw.wasko@enso.org>
2022-02-11 13:18:51 +03:00
[3249]: https://github.com/enso-org/enso/pull/3249
Debug Mode for Graph Editor (#3264)
2022-02-14 13:19:08 +03:00
[3264]: https://github.com/enso-org/enso/pull/3264
Adding Text.at and Text.is_digit functions (#3269) * Add Text.at function * Add tests for Text.at * Add tests for Text.is_digit * Change log * Avoid memory allocation
2022-02-14 12:03:55 +03:00
[3269]: https://github.com/enso-org/enso/pull/3269
Properly expose stacktraces and related data to user code (#3271)
2022-02-16 10:36:19 +03:00
[3271]: https://github.com/enso-org/enso/pull/3271
Implement Vector.flatten (#3259)
2022-02-15 18:16:08 +03:00
[3259]: https://github.com/enso-org/enso/pull/3259
Restrict Graph Editor Zoom (#3295) [Task link](#181181203). This is a reincarnation of PR [3273](https://github.com/enso-org/enso/pull/3273). The maximum zoom factor of Graph Editor is limited to 1.0x. It is not possible to zoom in from the default camera position. Debug Mode (activated with `ctrl-shift-d` shortcut) allows to zoom up to 100.0x (the previous behavior of Graph Editor). If you enable Debug Mode, then zoom in and disable Debug Mode - you won't see the immediate change of zoom factor back to 1.0x. But it will "jump" (with animation) back once you make a zoom in/out event with your controls. Video: https://user-images.githubusercontent.com/6566674/154037310-1d166737-353e-4ae6-aca1-f7840571ab16.mp4 # Important Notes This is a reincarnation of PR [3273](https://github.com/enso-org/enso/pull/3273). There are two changes since that PR: 1. Fixed bug with GeoMap zooming described [here](https://github.com/enso-org/enso/pull/3290). This is done by restricting `ZoomEvent` API so that it will never contain `amount` which is equal to `0.0`. 2. A few refactoring changes from https://github.com/enso-org/enso/pull/3289 to simplify code a bit.
2022-02-22 14:23:59 +03:00
[3273]: https://github.com/enso-org/enso/pull/3273
Improvement to the Natural Order Sort (#3276) * Improved Natural Order Data generator for benchmarking * Missing Import Benchmark script * Update Natural_Order.enso Restore missing ToDo * Changelog * PR Comments * PR Comments * Additional comments. * Correction
2022-02-16 20:40:33 +03:00
[3276]: https://github.com/enso-org/enso/pull/3276
Return creating node with (+) button & fix a regression (#3338) * Creating a new node with the (+) button (#3278) [The Task](https://www.pivotaltracker.com/story/show/180887253) A new (+) button on the left-bottom corner appeared. It may be clicked to open searcher in the middle of the scene, as an alternative to tab key. https://user-images.githubusercontent.com/3919101/154514279-7972ed6a-0203-47cb-9a09-82dba948cf2f.mp4 * The window_control_buttons::common was extracted to separate crate `ensogl-component-button` almost without change. * This includes a severe refactoring of adding nodes in general in the Graph Editor. The whole responsibility of adding new nodes (and starting their editing) was moved to Graph Editor - the Project View only reacts for GE events to show searcher properly. * The status bar was moved from the bottom-left corner to the middle-top of the scene. It does not collide with (+) button, and plays "notification" role anyway. * The `interface` debug scene was buggy. The problem was with one expression's span-tree. When I replaced it, the scene works. * I've removed "new searcher" API, as it is completely outdated. * I've changed code owners of integration tests to GUI team, as it is the team writing mostly the integration tests (int rust) * Fix regression #181528359 * Add docs & remove unused function * Fix & enable native Rust tests * Fix formatting Co-authored-by: Adam Obuchowicz <adam.obuchowicz@enso.org> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
2022-03-16 21:02:47 +03:00
[3278]: https://github.com/enso-org/enso/pull/3278
Adding Integer.Parse (#3283) * Integer parse via Longs * Integer parse via Longs * Benchmark for Number Parse * CHANGELOG.md and Natural Order * Expanded test set * Number base tests * Few more negative tests
2022-02-17 18:04:00 +03:00
[3283]: https://github.com/enso-org/enso/pull/3283
Ensure that `Text.compare_to` compares strings according to grapheme clusters (#3282) https://www.pivotaltracker.com/story/show/181175238
2022-02-17 20:09:41 +03:00
[3282]: https://github.com/enso-org/enso/pull/3282
Data analysts should be able to use `Text.contains` to check for substring using various matcher techniques. (#3285) * Add matching mode definitions * Add stub for new method API and an initial test suite * Fix tests, implement exact matching * Implement Regex matching * changelog * Add benchmarks * Wokraround for case insensitive regex locale support * minor tweaks * Unify Case_Insensitive * Update edge cases * Fix other affected places * minor style change * Add a problematic test * Add a regex test for a similar situation * Migrate to StringSearch:wq * Add test cases for scharfes S edge case * Add problematic Regex Unicode normalization test * Document the regex accents peculiarity * Do not apply the normalization in ASCII only mode * cr
2022-02-22 18:41:56 +03:00
[3285]: https://github.com/enso-org/enso/pull/3285
Text.take and Text.drop (#3287) Implementation of the Text take and drop APIs - Added `Range.contains` function - Added `Text_Sub_Range` type - Added `Text_Utils.index_of` and `Text_Utils.last_index_of` based on ICU StringSearcher
2022-02-22 21:50:59 +03:00
[3287]: https://github.com/enso-org/enso/pull/3287
Data analysts should be able to use `Text.starts_with` and `Text.ends_with` (#3292) Implements https://www.pivotaltracker.com/story/show/181265900
2022-02-23 19:48:33 +03:00
[3292]: https://github.com/enso-org/enso/pull/3292
Placement of newly opened Component Browser dictated by the mouse pointer. (#3301) Use a new algorithm for placement of new nodes in cases when: - a) there is no selected node, and the `TAB` key is pressed while the mouse pointer is near an existing node (especially in an area below an existing node); - b) a connection is dragged out from an existing node and dropped near the node (especially in an area below the node). In both cases mentioned above, the new node will now be placed in a location suggested by an internal algorithm, aligned to existing nodes. Specifically, the placement algorithm used is similar to when pressing `TAB` with a node selected. For more details, see: https://www.pivotaltracker.com/story/show/181076066 # Important Notes - Visible visualizations enabled with the "eye icon" button are treated as part of a node. (In case of nodes with errors, visualizations are not visible, and are not treated as part of a node.)
2022-03-31 17:16:28 +03:00
[3301]: https://github.com/enso-org/enso/pull/3301
Data analysts should be able to use `Text.to_case` to change the case of Text values (#3302) * Move to_upper_case and to_lower_case into to_case * Add an export, not sure about it * Implement title case TODO: some more tests would be good * Add more tests * explain title case * fix todo * changelog
2022-03-01 02:20:41 +03:00
[3302]: https://github.com/enso-org/enso/pull/3302
Table.group_by (#3305) Functioning group_by based of Enso Map. # Important Notes This is an initial version which will be used to establish the API. The grouping map will need to be moved to Java code for performance.
2022-03-01 19:18:11 +03:00
[3305]: https://github.com/enso-org/enso/pull/3305
Text.pad and Text.trim (#3309) Implements https://www.pivotaltracker.com/story/show/181265516
2022-03-02 20:19:39 +03:00
[3309]: https://github.com/enso-org/enso/pull/3309
Updating `Text.repeat` and adding `Text.*` (#3310) Updating the `Text.repeat` function: - fix issue with negative count - add * operator Add tests of the function.
2022-03-02 22:00:47 +03:00
[3310]: https://github.com/enso-org/enso/pull/3310
Update Electron (#3316) PR fixes the issue when the user is unable to sign in with Google. In the end, my assumption about the `User-Agent` header was correct and Google sign-in works with the recent Electron out of the box.
2022-03-10 10:44:19 +03:00
[3316]: https://github.com/enso-org/enso/pull/3316
Fix CHANGELOG after mergeconflict (#3320)
2022-03-07 12:13:20 +03:00
[3236]: https://github.com/enso-org/enso/pull/3236
[3311]: https://github.com/enso-org/enso/pull/3311
Added `compare_to` to True/False (#3317)
2022-03-08 16:24:04 +03:00
[3317]: https://github.com/enso-org/enso/pull/3317
Data analysts should be able to use `Text.location_of` to find indexes within string using various matchers (#3324) Implements https://www.pivotaltracker.com/n/projects/2539304/stories/181266029
2022-03-12 22:42:00 +03:00
[3318]: https://github.com/enso-org/enso/pull/3318
[3324]: https://github.com/enso-org/enso/pull/3324
Node searcher zoom & edited node growth/shrink animation (#3327) In this PR two things are implemented: 1. Node Searcher zoom factor (and therefore its size) is fixed no matter how you move the main camera. The node searcher is also positioned directly below currently edited node at all times. 2. Node growth/shrink animation when you start/finish node editing. After animation end the edited node zoom factor is also fixed and matches the zoom factor of the node searcher. See attached video with different ways of editing/creating nodes: https://user-images.githubusercontent.com/6566674/157348758-2880aa2b-494d-46e6-8eee-a22be84081ed.mp4 #### Technical details 1. Added several additional scene layers for separate rendering: `node_searcher`, `node_searcher_text`, `edited_node`, `edited_node_text`. Searcher is always rendered by `node_searcher` camera, edited node moves between its usual layers and `edited_node` layer. Because text rendering uses different API, all node components were modified to support change of the layer. 2. Also added `node_searcher` DOM layer, because documentation is implemented as a DOM object. 3. Added two FRP endpoints for `ensogl::Animation`: `on_end` and `set_value`. These endpoints are useful while implementing growth/shrink animation. 4. Added FRP endpoints for the `Camera2d`: `position` and `zoom` outputs. This allows to synchronize cameras easily using FRP networks. 5. Growth/shrink animation implemented in GraphEditor by blending two animations, similar to Node Snapping implementation. However, shrinking animation is a bit tricky to implement correctly, as we must always return node back to the `main` scene layer after editing is done.
2022-03-17 13:38:18 +03:00
[3327]: https://github.com/enso-org/enso/pull/3327
Refactor table.group_by to table.aggregate (#3339) Following UX work move to `table.aggregate` function.
2022-03-15 17:23:36 +03:00
[3339]: https://github.com/enso-org/enso/pull/3339
The library developer should be able to handle specific types of Panics while passing through others (#3344) Implements https://www.pivotaltracker.com/story/show/181569176 Also ensures that Dataflow Errors have proper stack traces (earlier they did not point at the right location).
2022-03-18 19:57:06 +03:00
[3344]: https://github.com/enso-org/enso/pull/3344
Opening Component Browser by clicking on the output port (#3346) Double-clicking a node's output port or clicking the port with a right mouse button (RMB) creates a new node aligned to the clicked node. #### Visuals The screencast below demonstrates the following features: - double-clicking the left mouse button on a node's output port; - clicking the right mouse button on a node's output port; - alignment of the nodes created as a result of the actions described above; - corner case: double-clicking (and RMB-clicking) on output ports of a "collapsed" ("enterable") node; - double-clicking on a "collapsed" ("enterable") node still allows entering the node when done over an area of the node that is not the node's output port; - basic support for nodes with multiple output ports (shown on the `interface` demo scene). https://user-images.githubusercontent.com/273837/158991856-e0faa5f0-9d2f-44bd-bddd-ba314977db6e.mov The supplementary screencast below demonstrates that double-clicking or RMB-clicking a node's output port cancels the action of dragging a new connection from a node. https://user-images.githubusercontent.com/273837/158998097-100aed42-37ff-4467-939f-2b755ef0d3dc.mov https://www.pivotaltracker.com/story/show/181076145 # Important Notes - The "double-clicking a node" shortcut was previously used to allow entering a "collapsed" node (for example, a node created by pressing the `cmd+g` keyboard shortcut after selecting a group of nodes). This PR keeps that functionality when the user double-clicks on a node, as long as the mouse is not positioned over the node's output ports. - The support for nodes with multiple output ports is currently very basic. The information about a port (`Crumb`) is passed into the `create_node` function, but it is not passed further to `NodeSource`. The Node Searcher currently does not support passing port information through `NodeSource`.
2022-03-21 18:08:17 +03:00
[3346]: https://github.com/enso-org/enso/pull/3346
Refactor Aggregate Column (#3349) - Make it easier to understand the computations. - Fix issue with First. - Improve quote handling in Concatenate - Added validation and warnings to input
2022-03-22 21:18:46 +03:00
[3349]: https://github.com/enso-org/enso/pull/3349
Placement of newly opened Component Browser when nodes are selected (#3361) When a new node is created with the <kbd>TAB</kbd> key or by clicking the `(+)` on-screen button while multiple nodes are selected, place the new node below all the selected nodes. (Previously, the new node was placed below the node that was selected earliest.) Additionally, when placing a new node below an existing non-error node with a visualization enabled, place the new node below the visualization. (Previously, the new node was placed to the left of the visualization.) https://www.pivotaltracker.com/story/show/180887079 #### Visuals The following screencast demonstrates the feature on various arrangements of selected nodes, with visualization enabled and disabled. https://user-images.githubusercontent.com/273837/159971452-148aa4d7-c0f3-4b48-871a-a2783989f403.mov The following screencast demonstrates that new nodes created by double-clicking an output port of a node with visualization enabled are now placed below the visualization: https://user-images.githubusercontent.com/273837/160107733-e3f7d0f9-0161-49d1-8cbd-06e18c843a20.mov # Important Notes - Some refactorings that were needed for this PR were ported from the #3301 PR: - the code responsible for calculating the positions of new nodes was moved to a separate module (`new_node_position`); - the `free_place_finder` module was made a submodule of the `new_node_position` module, due to the latter being its only user.
2022-03-31 23:17:04 +03:00
[3361]: https://github.com/enso-org/enso/pull/3361
Moving Aggregation to Java (#3364)
2022-04-04 12:12:48 +03:00
[3364]: https://github.com/enso-org/enso/pull/3364
Component Group View with static header and without icons (#3373) Add an initial version of the visual component for displaying the Component Group View. The component contains a header (for displaying the Group Name) and a list of labels (for displaying the component names). https://www.pivotaltracker.com/story/show/181724889 #### Visuals A screenshot from a debug scene demonstrating the component: <img width="251" alt="Screenshot 2022-04-13 at 20 07 56" src="https://user-images.githubusercontent.com/273837/163243304-21c3ad78-4813-4368-b3bb-844d979da699.png"> Screenshots from other debug scenes (`list_view` and `text_area`), demonstrating that the other components still display correctly: <img width="202" alt="Screenshot 2022-04-13 at 20 08 56" src="https://user-images.githubusercontent.com/273837/163243428-de9dc1c7-5a9f-45e0-9325-db60cece9768.png"> <img width="403" alt="Screenshot 2022-04-13 at 20 08 48" src="https://user-images.githubusercontent.com/273837/163243432-895061d9-5bd9-4349-8679-eb63b0f6724d.png"> A screenshot of the Node Searcher's list, showing that long entries in a ListView are now truncated, and an ellipsis character is added in place of removed characters: <img width="651" alt="Screenshot 2022-04-13 at 20 10 16" src="https://user-images.githubusercontent.com/273837/163243664-5b671969-7aa0-4bef-8fd2-825602d85848.png"> # Important Notes - Adding support for the text truncation feature in `ListView` required some changes in the`list_view::Entry`-related APIs. - An embedded font was added (DejaVuSans-Bold) for use in the Component Group View debug scene, and 5 unused embedded fonts were removed.
2022-04-14 13:37:40 +03:00
[3373]: https://github.com/enso-org/enso/pull/3373
Data analysts should be able to reverse strings using `Text.reverse` (#3377) This commit implements `Text.reverse` as an extension on `Text`. `Text.reverse` reverses strings. For example: `"Hello World!".reverse` results in `"!dlroW olleH"`. Strings are reversed by their Extended Grapheme Clusters not by their characters. This has some performance implications because we need to find these grapheme cluster boundaries when iterating. To do so, `BreakIterator.getCharacterInstance` is used. Implements: https://www.pivotaltracker.com/n/projects/2539304/stories/181265419
2022-04-05 19:45:56 +03:00
[3377]: https://github.com/enso-org/enso/pull/3377
Applying Magnet Alignment Algorithm to newly opened Component Browser (#3366) [Task link](https://www.pivotaltracker.com/story/show/181076594) This PR enables new node position adjustment using the Magnet Alignment algorithm for the following cases: - When creating node with (+) button without nodes selected - When creating node with "Mouse pointer dictated placement." not under the source node - When the node is pushed left due to lack of space - only horizontally The size of the `alignment area` around node is slightly enlarged, so that it's impossible to create a node that is being too close to other nodes. Videos with AC demonstration: https://user-images.githubusercontent.com/6566674/160565491-818b1705-43f8-41ab-abad-047031b2f9e5.mp4 https://user-images.githubusercontent.com/6566674/160565501-d2d4ea85-68c7-4385-9681-701ab86fdd98.mp4 https://user-images.githubusercontent.com/6566674/160565535-9cbeadfe-397b-4cf8-802a-1ec4148a70a2.mp4
2022-04-05 14:22:29 +03:00
[3366]: https://github.com/enso-org/enso/pull/3366
Fix multiline code docparser (#3379) Changelog: - fix: docparser handles multiline code sections correctly - feat: split paragraphs into keyed sections
2022-04-06 07:39:58 +03:00
[3379]: https://github.com/enso-org/enso/pull/3379
Add benchmark for `Text.reverse` with strings of varying length (#3381) This pull request adds a benchmark for the `Text.reverse` function added in #3377 as part of https://www.pivotaltracker.com/n/projects/2539304/stories/181265419. Per discussion with @jdunkerley on Discord it is useful to have this benchmark as this is a low-level item we want to track.
2022-04-05 20:59:21 +03:00
[3381]: https://github.com/enso-org/enso/pull/3381
Fill component groups of standard libraries (#3391) Changelog: - add: component groups to package descriptions - add: `executionContext/getComponentGroups` method that returns component groups of libraries that are currently loaded - doc: cleanup unimplemented undo/redo commands - refactor: internal component groups datatype
2022-04-14 16:12:18 +03:00
[3391]: https://github.com/enso-org/enso/pull/3391
Extend Aggregate_Spec test suite with tests for missed edge-cases to ensure the feature is well-tested on all backends (#3383) Implements https://www.pivotaltracker.com/story/show/181805693 and finishes the basic set of features of the Aggregate component. Still not all aggregations are supported everywhere, because for example SQLite has quite limited support for aggregations. Currently the workaround is to bring the table into memory (if possible) and perform the computation locally. Later on, we may add more complex generator features to emulate the missing aggregations with complex sub-queries.
2022-04-12 14:02:01 +03:00
[3383]: https://github.com/enso-org/enso/pull/3383
SDF-based mechanism for making letters bold (#3385) Fixes [181641027](https://www.pivotaltracker.com/story/show/181641027). There are new methods of text::Area for making some letters bolder, without moving them nor any other letters in the line. Tested on DejaVuSans text: ![image](https://user-images.githubusercontent.com/3919101/162199723-524f7560-535f-4c98-bcb4-6b760ad8cb04.png) ![image](https://user-images.githubusercontent.com/3919101/162199806-e6582c56-3071-4653-8ad2-114df86cd6b7.png) ![image](https://user-images.githubusercontent.com/3919101/162199880-1836e902-8663-4696-bcb7-2b15c3c243c6.png) On MacOS: <img width="824" alt="Screenshot 2022-04-07 at 14 54 40" src="https://user-images.githubusercontent.com/3919101/162203730-ffda3096-7aab-443f-a45a-bfa18784ba36.png"> <img width="379" alt="Screenshot 2022-04-07 at 14 54 52" src="https://user-images.githubusercontent.com/3919101/162203751-f5ca2e26-fdb6-4521-9821-999111b80ac0.png"> <img width="160" alt="Screenshot 2022-04-07 at 14 54 58" src="https://user-images.githubusercontent.com/3919101/162203769-3c367f81-67bb-48aa-994c-42eeb131017e.png">
2022-04-12 20:39:08 +03:00
[3385]: https://github.com/enso-org/enso/pull/3385
Implement Events Monitor (#3392) PR adds a monitor that handles messages between the language server and the runtime and dumps them as a CSV file `/tmp/enso-api-events-*********.csv` ``` UTC timestamp,Direction,Request Id,Message class ``` # Important Notes :warning: Monitor is enabled when the log level is set to trace. You should pass `-vv` (very verbose) option to the backend when starting IDE ``` enso -- -vv ```
2022-04-12 18:17:47 +03:00
[3392]: https://github.com/enso-org/enso/pull/3392
Data analysts should be able to use `Text.replace` to substitute parts of the text (#3393) Implements https://www.pivotaltracker.com/story/show/181266274
2022-04-13 22:21:47 +03:00
[3393]: https://github.com/enso-org/enso/pull/3393
Restructuring for File.read (#3390) - Added Encoding type - Added `Text.bytes`, `Text.from_bytes` with Encoding support - Renamed `File.read` to `File.read_text` - Renamed `File.write` to `File.write_text` - Added Encoding support to `File.read_text` and `File.write_text` - Added warnings to invalid encodings
2022-04-19 19:50:03 +03:00
[3390]: https://github.com/enso-org/enso/pull/3390
Review Range and Interval, resolve infinite loop issue (#3408) Implements: https://www.pivotaltracker.com/story/show/181652841
2022-04-20 19:22:01 +03:00
[3408]: https://github.com/enso-org/enso/pull/3408
Data analysts should be able to use `Text.split`, `Text.lines` and `Text.words` to break up strings (#3415) Implements https://www.pivotaltracker.com/story/show/181266184 ### Important Notes Changed example image download to only proceed if the file did not exist before - thus cutting on the build time (the build used to download it _every_ time - which completely failed the build if network is down). A redownload can be forced by performing a fresh repository checkout.
2022-04-26 18:22:53 +03:00
[3415]: https://github.com/enso-org/enso/pull/3415
Improve support for reading Delimited files (#3424) Implements https://www.pivotaltracker.com/story/show/181823957
2022-04-29 20:12:19 +03:00
[3424]: https://github.com/enso-org/enso/pull/3424
File_Format.Excel work (#3425) - Read in Excel files following the specification. - Support for XLSX and XLS formats. - Ability to select ranges and sheets. - Skip Rows and Row Limits. # Important Notes - Minor fix to DelimitedReader for Windows
2022-05-06 16:21:10 +03:00
[3425]: https://github.com/enso-org/enso/pull/3425
Delimited File Encoding (#3430) Implements https://www.pivotaltracker.com/story/show/181998375
2022-05-11 01:44:05 +03:00
[3430]: https://github.com/enso-org/enso/pull/3430
Statistics on a Vector (#3442) - Implements various statistics on Vector # Important Notes Some minor codebase improvements: - Some tweaks to Any/Nothing to improve performance - Fixed bug in ObjectComparator - Added if_nothing - Removed Group_By_Key
2022-05-11 16:25:06 +03:00
[3442]: https://github.com/enso-org/enso/pull/3442
Cleanup Ref - get/put (#3457) The change promotes static methods of `Ref`, `get` and `put`, to be methods of `Ref` type. The change also removes `Ref` module from the default namespace. Had to mostly c&p functional dispatch for now, in order for the methods to be found. Will auto-generate that code as part of builtins system. Related to https://www.pivotaltracker.com/story/show/182138899
2022-05-17 13:26:36 +03:00
[3457]: https://github.com/enso-org/enso/pull/3457
Parsing values with known types (#3455) Implements https://www.pivotaltracker.com/story/show/181824146
2022-05-18 18:27:48 +03:00
[3455]: https://github.com/enso-org/enso/pull/3455
Refactor methods of Managed_Resource (#3460) Promoted `with`, `take`, `finalize` to be methods of Managed_Resource rather than static methods always taking `resource`, for consistency reasons. This required function dispatch boilerplate, similarly to `Ref`. In future iterations we will address this boilerplate code. Related to https://www.pivotaltracker.com/story/show/182212217
2022-05-18 20:27:42 +03:00
[3460]: https://github.com/enso-org/enso/pull/3460
Automatic inference of value types when parsing table columns (#3462) Implements https://www.pivotaltracker.com/story/show/182199966
2022-05-20 18:08:36 +03:00
[3462]: https://github.com/enso-org/enso/pull/3462
Integrate value parsing with Delimited file reading (#3463) Implements https://www.pivotaltracker.com/story/show/182200028
2022-05-24 18:59:00 +03:00
[3463]: https://github.com/enso-org/enso/pull/3463
The user should be able to have the headers Inferred when reading a Delimited file (#3472) Implements https://www.pivotaltracker.com/story/show/181986831
2022-05-25 16:29:17 +03:00
[3472]: https://github.com/enso-org/enso/pull/3472
Fix depth-ordering update (#3486) There are two dirty flags in layers: depth_order_dirty and element_depth_order_dirty - one marking changed in Layer, second marking change in one of sublayers. The depth_order_dirty has a proper callback for setting element_depth_order_dirty of its parent. However, the latter did not propagate up. I fixed it by adding callback for element_depth_order_dirty which sets the depth_order_dirty of the parent. # Important Notes * The question to @wdanilo : is it possible, that I can propagate dirty directly to element_depth_order_dirty, without setting depth_order_dirty? As far as I understand the code, it would also work (and we would omit some unnecessary updates). * I tried to leave some logs, but I don't feel how to do that: the tooling I used was very specific, only the concrete ids of symbols and layers were logged, and I don't know how to generalize it.
2022-05-30 13:32:43 +03:00
[3486]: https://github.com/enso-org/enso/pull/3486
Implement Table from Text conversion (#3478) Implements https://www.pivotaltracker.com/story/show/181824168
2022-05-26 15:04:25 +03:00
[3478]: https://github.com/enso-org/enso/pull/3478
Rank Data, Correlation, Covariance, R Squared (#3484) - Added new `Statistic`s: Covariance, Pearson, Spearman, R Squared - Added `covariance_matrix` function - Added `pearson_correlation` function to compute correlation matrix - Added `rank_data` and Rank_Method type to create rankings of a Vector - Added `spearman_correlation` function to compute Spearman Rank correlation matrix # Important Notes - Added `Panic.throw_wrapped_if_error` and `Panic.handle_wrapped_dataflow_error` to help with errors within a loop. - Removed `Array.set_at` use from `Table.Vector_Builder`
2022-05-30 20:13:06 +03:00
[3484]: https://github.com/enso-org/enso/pull/3484
Implement `Table.order_by` for SQLite and the common scaffolding for all backends (#3502) Implements the common and SQLite parts of https://www.pivotaltracker.com/story/show/182195405
2022-06-06 13:56:52 +03:00
[3502]: https://github.com/enso-org/enso/pull/3502
Improve database `Table.order_by` (#3514) Implements https://www.pivotaltracker.com/story/show/182195405 Adds support for the Postgres dialect and simple case insensitive collation for SQLite.
2022-06-07 15:31:55 +03:00
[3514]: https://github.com/enso-org/enso/pull/3514
Implement In-Memory Table order_by (#3515) Implemented the `order_by` function with support for all modes of operation. Added support for case insensitive natural order. # Important Notes - Improved MultiValueIndex/Key to not create loads of arrays. - Adjusted HashCode for MultiValueKey to have a simple algorithm. - Added Text_Utils.compare_normalized_ignoring_case to allow for case insensitive comparisons. - Fixed issues with ObjectComparator and added some unit tests for it.
2022-06-08 15:30:50 +03:00
[3515]: https://github.com/enso-org/enso/pull/3515
Basic changes to File_Format (#3516) Implements https://www.pivotaltracker.com/story/show/182308987
2022-06-08 12:53:18 +03:00
[3516]: https://github.com/enso-org/enso/pull/3516
Adjusting First and Last order_by to use Sort_Column_Selector (#3517)
2022-06-10 12:59:03 +03:00
[3517]: https://github.com/enso-org/enso/pull/3517
Add `Text.write` Function (#3518) Implements https://www.pivotaltracker.com/story/show/182309026
2022-06-13 12:11:46 +03:00
[3518]: https://github.com/enso-org/enso/pull/3518
Removing old functions and tidy up of Table types (#3519) - Removed `select` method. - Removed `group` method. - Removed `Aggregate_Table` type. - Removed `Order_Rule` type. - Removed `sort` method from Table. - Expanded comments on `order_by`. - Update comment on `aggregate` on Database. - Update Visualisation to use new APIs. - Updated Data Science examples to use new APIs. - Moved Examples test out of Tests to own test. # Important Notes Need to get Examples_Tests added to CI.
2022-06-14 16:37:20 +03:00
[3519]: https://github.com/enso-org/enso/pull/3519
Update Excel reading API (#3523) - Remove `from_xls` and `from_xlsx`. - Add `headers` support to `File_Format.Excel`. - Altered default read for Excel to be the first sheet. - Altered behavior so that single cells grow down and right when reading sheet. - Altered `Excel_Range` so knows if single cell or 1x1 range address. # Important Notes - Renamed `Range` to `Cell_Range` to avoid name clash.
2022-06-21 16:39:32 +03:00
[3523]: https://github.com/enso-org/enso/pull/3523
Implement value formatting and writing new files in Delimited format. (#3528) Implements https://www.pivotaltracker.com/story/show/182309429 and https://www.pivotaltracker.com/story/show/182309573
2022-06-23 19:51:52 +03:00
[3528]: https://github.com/enso-org/enso/pull/3528
Component list panel integration (#3530) This PR contains all work for finishing integration of first Component List Panel in the IDE: * It adds a stub for the whole Component Browser View. The documentation panel is re-used from the old searcher. * It has the presenter implementation, integrating the view with Hierarchical Component List from the controller. * It extends the View API, so the integration is possible, making use of Component Group Set wrapper. * The selection integration was also merged into this PR, because it depended on the API extension mentioned above. However, we should avoid such practice in the future. https://user-images.githubusercontent.com/3919101/177816427-8c4285b4-8941-4048-a400-52f4acf77a9f.mp4 # Important Notes There are some known issues, to-be-fixed in the future. * The performance is bad. It should be improved with new text::Area, and the decent one shall come with [GridView inside component browser](https://www.pivotaltracker.com/story/show/182561072) * There is no keyboard navigation. It should also be delivered with [GridView](https://www.pivotaltracker.com/story/show/182561072). * The Favorites section is not [filtered out by node source type](https://www.pivotaltracker.com/story/show/182661634).
2022-07-14 15:00:52 +03:00
[3530]: https://github.com/enso-org/enso/pull/3530
Update `Database.connect` to match new API (#3542) Initial work restructuring the `Database.connect` API - New SQLite API with support for InMemory. - Updated PostgreSQL API with SSL and Client Certificate Support. - Updated Redshift API. # Important Notes Follow up tasks: - PostgreSQL SSL additional testing. - Driver version updating. - `.pgpass` support.
2022-07-04 23:26:44 +03:00
[3542]: https://github.com/enso-org/enso/pull/3542
Adding write support to `File_Format.Excel` (#3551) Support for writing tables to Excel. # Important Notes Has custom support for Error mode as will allow appending a new table in this mode to the file.
2022-07-04 21:32:16 +03:00
[3551]: https://github.com/enso-org/enso/pull/3551
Pan camera to created nodes. (#3552) If a node created by the user gets placed off-screen, the screen's camera is panned to make the node visible. https://www.pivotaltracker.com/story/show/181188687 #### Visuals A screencast showing a number of node creation scenarios when the camera is panned to the newly created node, including when zoomed out. https://user-images.githubusercontent.com/273837/177169716-50a12b0a-c742-4b01-9766-56206e7938b9.mov # Important Notes - Camera is panned also if the node is only partially visible, or if there's not enough free space visible around the node. The specific amount of free space that needs to be visible around a newly created node is configured in the theme. - If the screen area is so small that the node cannot be fully fit in it (either horizontally or vertically), showing the left and top boundaries of the node's area takes priority over showing the corresponding opposite edges.
2022-07-06 13:33:35 +03:00
[3552]: https://github.com/enso-org/enso/pull/3552
Implementing basic functions (#3554) The language specification suggests to add [five basic functions into the standard library](https://github.com/enso-org/design/blob/wip/wd/enso-spec/epics/enso-spec-1.0/05.%20Functions.md#useful-functions-in-the-standard-library). `identity`, `flip`, `const`, `curry` & `uncurry`. # Important Notes The new functions are being added into existing `Function.enso` file. That may not be the best place, but it is not clear from the [design spec](https://github.com/enso-org/design/blob/wip/wd/enso-spec/epics/enso-spec-1.0/05.%20Functions.md#useful-functions-in-the-standard-library) how they are supposed to be imported. I can move them wherever needed. There is a documentation provided for each of the functions, but I am not sure how to verify it is correct. Do we generate the documentation for stdlib somehow?
2022-07-11 13:30:44 +03:00
[3554]: https://github.com/enso-org/enso/pull/3554
Adding Append support to Excel.Write (#3558) Adds support for appending to an existing Excel table. # Important Notes - Renamed `Column_Mapping` to `Column_Name_Mapping` - Changed new type name to `Map_Column` - Added last modified time and creation time to `File`.
2022-07-07 09:41:33 +03:00
[3558]: https://github.com/enso-org/enso/pull/3558
[3564]: https://github.com/enso-org/enso/pull/3564
Allow filtering caught error type in `Error.catch` (#3574) More and more often I need a way to only recover a specific type of a dataflow error (in a similar manner as with panics). So the API for `Error.catch` has been amended to more closely resemble `Panic.catch`, allowing to handle only specific types of dataflow errors, passing others through unchanged. The default is `Any`, meaning all errors are caught by default, and the behaviour of `x.catch` remains unchanged.
2022-07-11 11:26:44 +03:00
[3574]: https://github.com/enso-org/enso/pull/3574
Add appending support for Delimited files (#3573) Implements https://www.pivotaltracker.com/story/show/182309839
2022-07-11 15:36:01 +03:00
[3573]: https://github.com/enso-org/enso/pull/3573
Move `write_bytes` to be part of `Vector`. (#3583) Updates `write_bytes` API to be part of `Vector` and to conform to `write` APIs. # Important Notes Ensures doesn't touch the file if an invalid byte array.
2022-07-14 14:30:40 +03:00
[3583]: https://github.com/enso-org/enso/pull/3583
Add new options to the Delimited format (#3581) Implements https://www.pivotaltracker.com/story/show/182662195 and https://www.pivotaltracker.com/story/show/182651884
2022-07-14 18:01:26 +03:00
[3581]: https://github.com/enso-org/enso/pull/3581
Grid View with Scrolling (#3588) **Note**: This PR also contains content of previous Grid View PR. We decided to discard the previous, because this one did some refactoring of old one, and it's not a big addition. Added a scrollable::GridView component, which just embeds the GridView in ScrollArea. Also, re-worked the idea of text layers. https://user-images.githubusercontent.com/3919101/179020359-512ee127-c333-4f86-bff5-f1cb4154e03c.mp4
2022-07-19 11:39:23 +03:00
[3588]: https://github.com/enso-org/enso/pull/3588
Type name case fixes: (#3590) - MacOS => Mac_OS - PostgreSQL => Postgres - SQLite => SQLite (align a few) - InMemory => In_Memory - PointData => Point_Data - Io_Error => IO_Error - Standard.Table.Io => Standard.Table.IO In Tests: - MyError => My_Error - NotFoo => Not_Foo
2022-07-19 17:09:09 +03:00
[3590]: https://github.com/enso-org/enso/pull/3590
Add support for `.pgpass` to PostgreSQL (#3593) Implements https://www.pivotaltracker.com/story/show/182582924
2022-07-21 16:32:37 +03:00
[3593]: https://github.com/enso-org/enso/pull/3593
Add Linear Regression support for Vectors. (#3601) Adds least squares regression APIs. Covers the basic 4 trend line types from Excel (doesn't cover Polynomial or Moving Average). Removes the old `Model` from the `Standard.Table`.
2022-07-22 11:41:17 +03:00
[3601]: https://github.com/enso-org/enso/pull/3601
Create `Index_Sub_Range` type and update `Text.take` and `Text.drop` (#3617)
2022-08-03 14:41:34 +03:00
[3617]: https://github.com/enso-org/enso/pull/3617
Use Vector.from_polyglot_array to make Vectors backed by polyglot arrays (#3628) Use Proxy_Polyglot_Array as a proxy for polyglot arrays, thus unifying the way the underlying array is accessed in Vector. Used the opportunity to cleanup builtin lookup, which now actually respects what is defined in the body of @Builtin_Method annotation. Also discovered that polyglot null values (in JS, Python and R) were leaking to Enso. Fixed that by doing explicit translation to `Nothing`. https://www.pivotaltracker.com/story/show/181123986
2022-08-24 00:13:16 +03:00
[3628]: https://github.com/enso-org/enso/pull/3628
Add `Vector.take` and `Vector.drop` functions (#3629) Implements https://www.pivotaltracker.com/story/show/182307048
2022-08-10 19:02:02 +03:00
[3629]: https://github.com/enso-org/enso/pull/3629
Restructuring `Database.Connection` to allow for database specific types. (#3632) - Added `databases`, `database`, `set_database`. - Added `schemas`, `schema`, `set_schema`. - Added `table_types`, - Added `tables`. - Moved the vast majority of the connection work into a lower level `JDBC_Connection` object. - `Connection` represents the standard API for database connections and provides a base JDBC implementation. - `SQLite_Connection` has the `Connection` API but with custom `databases` and `schemas` methods for SQLite. - `Postgres_Connection` has the `Connection` API but with custom `set_database`, `databases`, `set_schema` and `schemas` methods for Postgres. - Updated `Redshift` - no public API change.
2022-09-07 20:32:28 +03:00
[3632]: https://github.com/enso-org/enso/pull/3632
Adding DateTime part functions (#3669) - Added `Zone`, `Date_Time` and `Time_Of_Day` to `Standard.Base`. - Renamed `Zone` to `Time_Zone`. - Added `century`. - Added `is_leap_year`. - Added `length_of_year`. - Added `length_of_month`. - Added `quarter`. - Added `day_of_year`. - Added `Day_Of_Week` type and `day_of_week` function. - Updated `week_of_year` to support ISO. # Important Notes - Had to pass locale to formatter for date/time tests to work on my PC. - Changed default of `week_of_year` to use ISO.
2022-08-26 18:47:58 +03:00
[3641]: https://github.com/enso-org/enso/pull/3641
Short hand version for `order_by` (#3643) Implements https://www.pivotaltracker.com/story/show/182868310
2022-08-16 18:41:37 +03:00
[3643]: https://github.com/enso-org/enso/pull/3643
Add key functions to Table to make it act as [Column] (#3644) Implements https://www.pivotaltracker.com/story/show/181370836
2022-08-18 15:33:02 +03:00
[3644]: https://github.com/enso-org/enso/pull/3644
Adding DateTime part functions (#3669) - Added `Zone`, `Date_Time` and `Time_Of_Day` to `Standard.Base`. - Renamed `Zone` to `Time_Zone`. - Added `century`. - Added `is_leap_year`. - Added `length_of_year`. - Added `length_of_month`. - Added `quarter`. - Added `day_of_year`. - Added `Day_Of_Week` type and `day_of_week` function. - Updated `week_of_year` to support ISO. # Important Notes - Had to pass locale to formatter for date/time tests to work on my PC. - Changed default of `week_of_year` to use ISO.
2022-08-26 18:47:58 +03:00
[3645]: https://github.com/enso-org/enso/pull/3645
Handling exceptions in IDE main to avoid entering "zombie process" state. (#3648) This is meant to address https://www.pivotaltracker.com/story/show/182691027.
2022-08-16 15:56:08 +03:00
[3648]: https://github.com/enso-org/enso/pull/3648
IDE uses new visualization API (#3661)
2022-09-01 15:33:46 +03:00
[3661]: https://github.com/enso-org/enso/pull/3661
Split long lines to 1024 long chunks (#3665) Avoid long lines when using `dom().set_inner_text` - rather split the long lines to 1024 chunks and insert them as individual `<div>` elements. # Important Notes I was testing the behavior on following program: ``` from Standard.Base import all import Standard.Base.Data.Statistics import Standard.Visualization main = number1 = 200000 operator1 = 0.up_to number1 . to_vector . map .noise operator2 = operator1.sort operator3 = operator2.to_text ``` before my change the visualization of `operator3` was blank. With my change it gets filled with data.
2022-08-29 11:02:33 +03:00
[3665]: https://github.com/enso-org/enso/pull/3665
Remove `Array.set_at` (#3634) Implements https://www.pivotaltracker.com/story/show/182879865 # Important Notes Note that removing `set_at` still does not make our arrays fully immutable - `Array.copy` can still be used to mutate them.
2022-08-26 12:34:33 +03:00
[3634]: https://github.com/enso-org/enso/pull/3634
Improved Vector/Array interop (#3667) `Vector` type is now a builtin type. This requires a bunch of additional builtin methods for its creation: - Use `Vector.from_array` to convert any array-like structure into a `Vector` [by copy](https://github.com/enso-org/enso/pull/3667/commits/f628b28f5ffa0bcdceb64a7604317b2f7aee58bd) - Use (already existing) `Vector.from_polyglot_array` to convert any array-like structure into a `Vector` **without** copying - Use (already existing) `Vector.fill 1 item` to create a singleton `Vector` Additional, for pattern matching purposes, we had to implement a `VectorBranchNode`. Use following to match on `x` being an instance of `Vector` type: ``` import Standard.Base.Data.Vector size = case x of Vector.Vector -> x.length _ -> 0 ``` Finally, `VectorLiterals` pass that transforms `[1,2,3]` to (roughly) ``` a1 = 1 a2 = 2 a3 = 3 Vector (Array (a1,a2, a3)) ``` had to be modified to generate ``` a1 = 1 a2 = 2 a3 = 3 Vector.from_array (Array (a1, a2, a3)) ``` instead to accomodate to the API changes. As of 025acaa676d2d020ef368405531d3a3cf8ea73de all the known CI checks passes. Let's start the review. # Important Notes Matching in `case` statement is currently done via `Vector_Data`. Use: ``` case x of Vector.Vector_Data -> True ``` until a better alternative is found.
2022-09-13 06:07:17 +03:00
[3667]: https://github.com/enso-org/enso/pull/3667
Adding DateTime part functions (#3669) - Added `Zone`, `Date_Time` and `Time_Of_Day` to `Standard.Base`. - Renamed `Zone` to `Time_Zone`. - Added `century`. - Added `is_leap_year`. - Added `length_of_year`. - Added `length_of_month`. - Added `quarter`. - Added `day_of_year`. - Added `Day_Of_Week` type and `day_of_week` function. - Updated `week_of_year` to support ISO. # Important Notes - Had to pass locale to formatter for date/time tests to work on my PC. - Changed default of `week_of_year` to use ISO.
2022-08-26 18:47:58 +03:00
[3669]: https://github.com/enso-org/enso/pull/3669
Add `Table.take` and `Table.drop` functions to In-Memory table (#3647) Implements https://www.pivotaltracker.com/story/show/182307347
2022-08-26 22:41:36 +03:00
[3647]: https://github.com/enso-org/enso/pull/3647
Add storage support for Date, Time and DateTime to InMemory table (#3673) Implements https://www.pivotaltracker.com/story/show/183080911
2022-09-01 01:06:29 +03:00
[3673]: https://github.com/enso-org/enso/pull/3673
Add `Table.distinct` function to In-Memory table (#3684) Implements https://www.pivotaltracker.com/story/show/182307143 # Important Notes - Modified standard library Java helpers dependencies so that `std-table` module depends on `std-base`, as a provided dependency. This is allowed, because `std-table` is used by the `Standard.Table` Enso module which depends on `Standard.Base` which ensures that the `std-base` is loaded onto the classpath, thus whenever `std-table` is loaded by `Standard.Table`, so is `std-base`. Thus we can rely on classes from `std-base` and its dependencies being _provided_ on the classpath. Thanks to that we can use utilities like `Text_Utils` also in `std-table`, avoiding code duplication. Additional advantage of that is that we don't need to specify ICU4J as a separate dependency for `std-table`, since it is 'taken' from `std-base` already - so we avoid including it in our build packages twice.
2022-09-07 15:28:41 +03:00
[3684]: https://github.com/enso-org/enso/pull/3684
Show Visualisation Preview when Selecting Item on Searcher (#3691) Implements [#182634050](https://www.pivotaltracker.com/story/show/182634050). Enables visualization previews for selections in the searcher. Works for the old Searcher and the new Component Browser, but it was easier to show the examples for the old searcher, as the suggestions seem to be better/faster available currently (this will improve with the new implementation using better strings and the new GridView). https://user-images.githubusercontent.com/1428930/188898560-fc4f412a-1529-49f7-9958-28bf5e01c001.mp4 Aborting an edit now also correctly reverts a node. https://user-images.githubusercontent.com/1428930/188898549-ddd41294-2571-4e2e-b6d5-909cbf71de04.mp4
2022-09-16 19:05:40 +03:00
[3691]: https://github.com/enso-org/enso/pull/3691
Add Period Start and End functions to Date and DateTime (#3695) Implements https://www.pivotaltracker.com/story/show/183081152
2022-09-13 12:51:08 +03:00
[3695]: https://github.com/enso-org/enso/pull/3695
Implement `type_of` (#3722) This change implements a simple `type_of` method that returns a type of a given value, including for polyglot objects. The change also allows for pattern matching on various time-related instances. It is a nice-to-have on its own, but it was primarily needed here to write some tests. For equality checks on types we currently can't use `==` due to a known _feature_ which essentially does wrong dispatching. This will be improved in the upcoming statics PR so we agreed that there is no point in duplicating that work and we can replace it later. Also, note that this PR changes `Meta.is_same_object`. Comparing types revealed that it was wrong when comparing polyglot wrappers over the same value.
2022-09-26 19:01:39 +03:00
[3722]: https://github.com/enso-org/enso/pull/3722
Add business days functions to Date and Date_Time (#3726) Implements https://www.pivotaltracker.com/story/show/183082087 # Important Notes - Removed unnecessary invocations of `Error.throw` improving performance of `Vector.distinct`. The time of the `add_work_days and work_days_until should be consistent with each other` test suite came down from 15s to 3s after the changes.
2022-09-22 11:31:15 +03:00
[3726]: https://github.com/enso-org/enso/pull/3726
Adjust Database connection to use query/read to access data. (#3727) Adjust Database connection API to align with new [design](https://github.com/enso-org/design/blob/wip/jd/database-read/epics/basic-libraries/database-read/design.md#querying-tables). - `query` replaces the old `access_table` and is expanded to support raw SQL queries. - `read` replaces `execute_query` and matches the API of `query`. - `to_dataframe` is renamed to `read`. # Important Notes Added support for `++` to concatenate a Text without wrapping in a `SQL.Code`.
2022-09-23 10:35:08 +03:00
[3727]: https://github.com/enso-org/enso/pull/3727
Add `Date_Period.Week` to `start_of` and `end_of` methods (#3733) Implements https://www.pivotaltracker.com/story/show/183349732
2022-09-24 01:14:35 +03:00
[3733]: https://github.com/enso-org/enso/pull/3733
Remove here keyword (#3749) Changelog - Remove `HERE` keyword - Replace `here` with module name when generating code
2022-09-29 21:34:17 +03:00
[3749]: https://github.com/enso-org/enso/pull/3749
Update Table API with new `filter` design (#3750) Implements https://www.pivotaltracker.com/story/show/183389855 # Important Notes Implements basic filter operations both In-Memory and for the Database backend, ensuring that existing tests can be adapted and keep working. Not all `Filter_Condition`s are implemented yet. Also implements significant part of https://www.pivotaltracker.com/story/show/183390314
2022-10-05 14:40:10 +03:00
[3750]: https://github.com/enso-org/enso/pull/3750
Add filtering by Filter_Condition to `Vector`, `Range` and `List` (#3770) Implements https://www.pivotaltracker.com/story/show/183389901
2022-10-07 07:02:54 +03:00
[3770]: https://github.com/enso-org/enso/pull/3770
Add `Is_Empty`, `Not_Empty`, `Like` and `Not_Like` to `Filter_Condition` (#3775) Implements https://www.pivotaltracker.com/story/show/183389890
2022-10-11 02:11:04 +03:00
[3775]: https://github.com/enso-org/enso/pull/3775
Duration type is a builtin type (#3759) - Reimplement the `Duration` type to a built-in type. - `Duration` is an interop type. - Allow Enso method dispatch on `Duration` interop coming from different languages. # Important Notes - The older `Duration` type should now be split into new `Duration` builtin type and a `Period` type. - This PR does not implement `Period` type, so all the `Period`-related functionality is currently not working, e.g., `Date - Period`. - This PR removes `Integer.milliseconds`, `Integer.seconds`, ..., `Integer.years` extension methods.
2022-10-14 21:08:08 +03:00
[3759]: https://github.com/enso-org/enso/pull/3759
Add `replace_text` method to In-Memory `Table` (#3793) Implements https://www.pivotaltracker.com/n/projects/2539304/stories/183415329
2022-10-14 18:42:29 +03:00
[3793]: https://github.com/enso-org/enso/pull/3793
Add support for `Is_In` and `Not_In` to `Filter_Condition` (#3790) Implements https://www.pivotaltracker.com/story/show/183389945
2022-10-15 14:29:59 +03:00
[3790]: https://github.com/enso-org/enso/pull/3790
Update `drop_missing_rows` to `filter_blank_rows` API. (#3805) Implements https://www.pivotaltracker.com/story/show/183390042 and https://www.pivotaltracker.com/story/show/183390370
2022-10-18 18:58:50 +03:00
[3805]: https://github.com/enso-org/enso/pull/3805
Add support for `Blank_Columns` to Table and Database (#3812) Implements https://www.pivotaltracker.com/story/show/183390281 and https://www.pivotaltracker.com/story/show/183390394
2022-10-20 12:11:08 +03:00
[3812]: https://github.com/enso-org/enso/pull/3812
Update shortcuts to reflect Component Browser design docs. (#3823) When no node is edited, `Enter` creates a new one (opening Component Browser). The shortcut for entering node was changed to `cmd + Enter`
2022-10-25 20:21:12 +03:00
[3823]: https://github.com/enso-org/enso/pull/3823
Create a Table `Row` Type and expose as a Vector on In-Memory Table with `.rows` property (#3827) Implements https://www.pivotaltracker.com/story/show/182307026
2022-10-26 14:21:33 +03:00
[3827]: https://github.com/enso-org/enso/pull/3827
Scrollbar LMB click and hold scrolling (#3824)
2022-10-26 21:20:44 +03:00
[3824]: https://github.com/enso-org/enso/pull/3824
Define Enso epoch start as 15th October 1582. (#3804) Define start of Enso epoch as 15th of October 1582 - start of the Gregorian calendar. # Important Notes - Some (Gregorian) calendar related functionalities within `Date` and `Date_Time` now produces a warning if the receiving Date/Date_Time is before the epoch start, e.g., `week_of_year`, `is_leap_year`, etc.
2022-10-27 13:16:43 +03:00
[3804]: https://github.com/enso-org/enso/pull/3804
Add `Period` type (#3818) This PR adds `Period` type, which is a date-only complement to `Duration` builtin type. # Important Notes - `Period` replaces `Date_Period`, and `Time_Period`. - Added shorthand constructors for `Duration` and `Period`. For example: `Period.days 10` instead of `Period.new days=10`. - `Period` can be compared to other `Period` in some cases, other cases throw an error.
2022-10-28 20:27:20 +03:00
[3818]: https://github.com/enso-org/enso/pull/3818
Wip/wdanilo/text shape system single scene 183406745 (#3776)
2022-11-03 10:35:06 +03:00
[3776]: https://github.com/enso-org/enso/pull/3776
Text rendering quality improvements. (#3855)
2022-11-08 21:15:05 +03:00
[3855]: https://github.com/enso-org/enso/pull/3855
add scroll overshoot bounce animation (#3836) Implements https://www.pivotaltracker.com/n/projects/2539304/stories/183390749 https://user-images.githubusercontent.com/919491/198984088-9c4f03db-922f-4503-83fa-f0301a11239e.mp4 # Important Notes - The overshoot bounce animation is implemented as a animation-like FRP mixin. It is currently defined using `define_endpoints` macro, but should be migrated to `define_endpoints_2` as soon as it supports "frp mixins" - definitions that extend external networks.
2022-11-07 13:50:47 +03:00
[3836]: https://github.com/enso-org/enso/pull/3836
Expanding Derived Columns and Expression Syntax (#3782) - Added expression ANTLR4 grammar and sbt based build. - Added expression support to `set` and `filter` on the Database and InMemory `Table`. - Added expression support to `aggregate` on the Database and InMemory `Table`. - Removed old aggregate functions (`sum`, `max`, `min` and `mean`) from `Column` types. - Adjusted database `Column` `+` operator to do concatenation (`||`) when text types. - Added power operator `^` to both `Column` types. - Adjust `iif` to allow for columns to be passed for `when_true` and `when_false` parameters. - Added `is_present` to database `Column` type. - Added `coalesce`, `min` and `max` functions to both `Column` types performing row based operation. - Added support for `Date`, `Time_Of_Day` and `Date_Time` constants in database. - Added `read` method to InMemory `Column` returning `self` (or a slice). # Important Notes - Moved approximate type computation to `SQL_Type`. - Fixed issue in `LongNumericOp` where it was always casting to a double. - Removed `head` from InMemory Table (still has `first` method).
2022-11-08 18:57:59 +03:00
[3782]: https://github.com/enso-org/enso/pull/3782
Focus management (#3863)
2022-11-14 12:09:49 +03:00
[3863]: https://github.com/enso-org/enso/pull/3863
Some minor fixes (#3874) - Allow `Map` to store a `Nothing` key (fixes `Vector.distinct` with a `Nothing`). - Add `column_names` method to `Table` as a shorthand. - Return data flow error when comparing with Nothing (not a Panic or a Polyglot exception). - Allow milli and micro second for DateTime and Time Of Day # Important Notes - Added a load of tests for the various comparison operators to Numbers_Spec.
2022-11-17 10:11:18 +03:00
[3874]: https://github.com/enso-org/enso/pull/3874
Numeric slider component with variable precision (#3852) This `Slider` component allows adjusting a numeric value with the mouse. The value is increased or decreased by clicking on the component and dragging it to the left or right. The `Slider` has a configurable default value. `Ctrl`+clicking on the component resets its value to that default. When the value is moved away from the default, the value is printed in **bold**. The `Slider` precision is increased or decreased by clicking the component and dragging upward or downward. This precision influences how quickly the value changes when the mouse moves horizontally, the steps in which the value is incremented or decremented, and the number of digits used to display the value. There is a margin around the component within which the precision is not changed. Beyond this margin, the precision is increased or decreased in powers of 10 (e.g. `0.1` -> `0.01` -> `0.001` when moving the mouse downwards, or `0.1` -> `1.0` -> `10.0` when moving the mouse upwards). The margin and distance between consecutive steps along the vertical axis are configurable. The value of the `Slider` is limited to a configurable range, and cannot be adjusted beyond that range. A colored bar fills the component to indicate the current value within the range. #### Video demonstration https://user-images.githubusercontent.com/117099775/202244982-2f6f419d-7281-41f6-8607-7e492ad25b46.mp4 #### Future additions This is the first iteration of the `Slider` component. Additional features are planned for the future: * Textual editing of the value. * Improved visual feedback on precision changes. * Additional out-of-range behaviors.
2022-11-24 18:37:03 +03:00
[3852]: https://github.com/enso-org/enso/pull/3852
Data analysts should be able to `Text.match`, `Text.match_all`, `Text.is_match` to find or check matches (#3841) Implements https://www.pivotaltracker.com/story/show/181266092 # Important Notes Also renaming `Text.location_of` and `Text.location_of_all` to `Text.locate` and `Text.locate_all`.
2022-11-19 01:17:42 +03:00
[3841]: https://github.com/enso-org/enso/pull/3841
Numeric slider component enhancement (#3885) This is an enhancement of the `Slider` component implemented in #3852. It adds the following features: * Tooltips and precision change hints * Selectable slider limit behaviors * Textual slider value editing * Vertical slider layout #### Tooltips An information tooltip can now be added to a slider, it is shown when the mouse hovers over the component. Additionally, a pop-up indicating the slider's precision appears when the slider's precision has been adjusted. https://user-images.githubusercontent.com/117099775/206148098-3b4dc059-18aa-4200-9ee0-5d4382363810.mp4 #### Slider limits The previous slider implementation clamped the adjusted value to the slider's minimum/maximum limits. Now the following behaviors are available: * Hard limits: Clamp the value to a range within the slider's limits. * Soft limits: The value can extend beyond the slider's limits. When this occurs, an overflow indicator will be displayed on the side of the limit that is exceeded. * Adaptive limits: The value can extend beyond the slider's limits. When this occurs, the exceeded limit will temporarily be adjusted to double the slider's range. This will be performed iteratively until the value falls within the extended limits. When a limit is extended and the value is adjusted to fit a smaller range, the extended limit will be iteratively halved until only the necessary range is covered. The slider's extended limits will never shrink to a range smaller than the original range. These behaviors can be set to the lower and upper limits of a slider independently. https://user-images.githubusercontent.com/117099775/206148139-6149c91d-ef49-4e2d-97f6-71084f52591c.mp4 #### Textual editing The slider's value can now be entered through a text input field. Double-click to edit the slider's current value. To confirm the edit press `enter`, or press `escape` to cancel the edit. If an invalid value is entered on confirmation the slider will revert to its value before the edit. The slider's precision will be adjusted based on the number of decimal places of the value entered. https://user-images.githubusercontent.com/117099775/206148170-d3fa4c82-6e73-4b1c-9be9-cb99979f7b70.mp4 #### Vertical layout The slider component now supports a vertical layout. In this case value adjustment is performed by a vertical mouse movement, and a horizontal movement adjusts the slider's precision. The slider's track now fills the component in a vertical direction, and the slider's label is displayed near the top end of the component. https://user-images.githubusercontent.com/117099775/206148211-0f176aaf-bc1b-45e2-afd7-0d28391aafcb.mp4 #### Scroll bar mode The slider component supports two indicator modes: * `Track`: The component is filled with a colored bar from the lower limit (empty) to the upper limit (full) dependent on the slider's value. * `Thumb`: The component contains a rounded indicator that moves along the slider from one end to the other, indicating the slider's value proportionally to the slider's limits. The width of the indicator is configurable. In addition, the value text, text entry, and precision adjustment can be turned off to provide a scroll bar appearance when used with the `Thumb` indicator. https://user-images.githubusercontent.com/117099775/206148261-ae291073-85e9-4082-9f91-39b65fecdc0f.mp4 #### Example scene shortcuts The example scene contains two shortcuts in order to evaluate the dynamic addition and removal of the slider components: * `CTRL+D` drops all the slider components that are added to the scene. * `CTRL+A` adds a new set of example slider components to the scene.
2022-12-12 11:53:19 +03:00
[3885]: https://github.com/enso-org/enso/pull/3885
Implement Lazy Text Visualisation. (#3910) Implements [#183453466](https://www.pivotaltracker.com/story/show/183453466). https://user-images.githubusercontent.com/1428930/203870063-dd9c3941-ce79-4ce9-a772-a2014e900b20.mp4 # Important Notes * the best laziness is used for `Text` type, which makes use of its internal representation to send data * any type will first compute its default string representation and then send the content of that lazy to the IDE * special handling of files and their content will be implemented in the future * size of the displayed text can be updated dynamically based on best effort information: if the backend does not yet know the full width/height of the text, it can update the IDE at any time and this will be handled gracefully by updating the scrollbar position and sizes.
2023-01-24 23:55:36 +03:00
[3910]: https://github.com/enso-org/enso/pull/3910
Implementing transpose and cross_tab for the InMemory table. (#3919) - Adds transpose and cross_tab to the In-Memory table. - Cross Tab is built on top of aggregate and hence allows for expressions and has same error trapping as in aggregate. # Important Notes Only basic tests have been implemented. Error and warning tests will be added as a follow up task.
2022-11-30 04:19:25 +03:00
[3919]: https://github.com/enso-org/enso/pull/3919
Make a VCS save on ctrl+s shortcut (#3923) Save a snapshot of the project directory to the VCS on `ctrl+s`. If the operation fails because the VCS was not initialized previously, it will try to initialize the VCS first and then save a snapshot.
2022-12-02 15:39:11 +03:00
[3923]: https://github.com/enso-org/enso/pull/3923
Visual indication of outdated VCS snapshot (#3950) This PR provides a visual indication of whether the project's current state differs from the most recent snapshot saved in the VCS. The project name displayed in the IDE changes to a darker text to indicate that the VCS snapshot is outdated, and back to a lighter text when the current project state corresponds to the last saved VCS snapshot. https://user-images.githubusercontent.com/117099775/208088438-20dfc2aa-2a7d-47bf-bc12-3d3dff7a4974.mp4 The outdated project snapshot indicator is set when: * A node is moved. * A node is added or removed. * The text editor is used to edit the text. * The project is auto-saved, and the auto-saved project state does not correspond to the last saved snapshot in the VCS. The outdated project snapshot indicator is cleared when: * A new project snapshot is successfully saved using `ctrl+s`. * The project is auto-saved, and the auto-saved project state is confirmed to correspond to the last saved snapshot in the VCS. This occurs, for example, when a project change is undone and the project is reverted to the last saved snapshot state. The auto-save events do not occur immediately after a project change but have a short delay, thus the VCS status update is affected by the same delay when triggered by an auto-save event.
2022-12-20 00:22:33 +03:00
[3950]: https://github.com/enso-org/enso/pull/3950
JSON Improvements, small Table stuff, Statistic in Enso not Java and few other minor bits. (#3964) - Aligned `compare_to` so returns `Type_Error` if `that` is wrong type for `Text`, `Ordering` and `Duration`. - Add `empty_object`, `empty_array`. `get_or_else`, `at`, `field_names` and `length` to `Json`. - Fix `Json` serialisation of NaN and Infinity (to "null"). - Added `length`, `at` and `to_vector` to Pair (allowing it to be treated as a Vector). - Added `running_fold` to the `Vector` and `Range`. - Added `first` and `last` to the `Vector.Builder`. - Allow `order_by` to take a single `Sort_Column` or have a mix of `Text` and `Sort_Column.Name` in a `Vector`. - Allow `select_columns_helper` to take a `Text` value. Allows for a single field in group_by in cross_tab. - Added `Patch` and `Custom` to HTTP_Method. - Added running `Statistic` calculation and moved more of the logic from Java to Enso. Performance seems similar to pure Java version now.
2022-12-14 22:40:27 +03:00
[3964]: https://github.com/enso-org/enso/pull/3964
Add a shortcut for interrupting the program (#3967) Add shortcuts for interrupting and restarting the program execution.
2022-12-12 20:48:42 +03:00
[3967]: https://github.com/enso-org/enso/pull/3967
Let JavaScript parse JSON and write JSON ... (#3987) Use JavaScript to parse and serialise to JSON. Parses to native Enso object. - `.to_json` now returns a `Text` of the JSON. - Json methods now `parse`, `stringify` and `from_pairs`. - New `JSON_Object` representing a JavaScript Object. - `.to_js_object` allows for types to custom serialize. Returning a `JS_Object`. - Default JSON format for Atom now has a `type` and `constructor` property (or method to call for as needed to deserialise). - Removed `.into` support for now. - Added JSON File Format and SPI to allow `Data.read` to work. - Added `Data.fetch` API for easy Web download. - Default visualization for JS Object trunctes, and made Vector default truncate children too. Fixes defect where types with no constructor crashed on `to_json` (e.g. `Matching_Mode.Last.to_json`. Adjusted default visualisation for Vector, so it doesn't serialise an array of arrays forever. Likewise, JS_Object default visualisation is truncated to a small subset. New convention: - `.get` returns `Nothing` if a key or index is not present. Takes an `other` argument allowing control of default. - `.at` error if key or index is not present. - `Nothing` gains a `get` method allowing for easy propagation.
2022-12-20 13:33:46 +03:00
[3987]: https://github.com/enso-org/enso/pull/3987
All Enso objects are hasheable (#3878) * Hash codes prototype * Remove Any.hash_code * Improve caching of hashcode in atoms * [WIP] Add Hash_Map type * Implement Any.hash_code builtin for primitives and vectors * Add some values to ValuesGenerator * Fix example docs on Time_Zone.new * [WIP] QuickFix for HashCodeTest before PR #3956 is merged * Fix hash code contract in HashCodeTest * Add times and dates values to HashCodeTest * Fix docs * Remove hashCodeForMetaInterop specialization * Introduce snapshoting of HashMapBuilder * Add unit tests for EnsoHashMap * Remove duplicate test in Map_Spec.enso * Hash_Map.to_vector caches result * Hash_Map_Spec is a copy of Map_Spec * Implement some methods in Hash_Map * Add equalsHashMaps specialization to EqualsAnyNode * get and insert operations are able to work with polyglot values * Implement rest of Hash_Map API * Add test that inserts elements with keys with same hash code * EnsoHashMap.toDisplayString use builder storage directly * Add separate specialization for host objects in EqualsAnyNode * Fix specialization for host objects in EqualsAnyNode * Add polyglot hash map tests * EconomicMap keeps reference to EqualsNode and HashCodeNode. Rather than passing these nodes to `get` and `insert` methods. * HashMapTest run in polyglot context * Fix containsKey index handling in snapshots * Remove snapshots field from EnsoHashMapBuilder * Prepare polyglot hash map handling. - Hash_Map builtin methods are separate nodes * Some bug fixes * Remove ForeignMapWrapper. We would have to wrap foreign maps in assignments for this to be efficient. * Improve performance of Hash_Map.get_builtin Also, if_nothing parameter is suspended * Remove to_flat_vector. Interop API requires nested vector (our previous to_vector implementation). Seems that I have misunderstood the docs the first time I read it. - to_vector does not sort the vector by keys by default * Fix polyglot hash maps method dispatch * Add tests that effectively test hash code implementation. Via hash map that behaves like a hash set. * Remove Hashcode_Spec * Add some polyglot tests * Add Text.== tests for NFD normalization * Fix NFD normalization bug in Text.java * Improve performance of EqualsAnyNode.equalsTexts specialization * Properly compute hash code for Atom and cache it * Fix Text specialization in HashCodeAnyNode * Add Hash_Map_Spec as part of all tests * Remove HashMapTest.java Providing all the infrastructure for all the needed Truffle nodes is no longer manageable. * Remove rest of identityHashCode message implementations * Replace old Map with Hash_Map * Add some docs * Add TruffleBoundaries * Formatting * Fix some tests to accept unsorted vector from Map.to_vector * Delete Map.first and Map.last methods * Add specialization for big integer hash * Introduce proper HashCodeTest and EqualsTest. - Use jUnit theories. - Call nodes directly * Fix some specializations for primitives in HashCodeAnyNode * Fix host object specialization * Remove Any.hash_code * Fix import in Map.enso * Update changelog * Reformat * Add truffle boundary to BigInteger.hashCode * Fix performance of HashCodeTest - initialize DataPoints just once * Fix MetaIsATest * Fix ValuesGenerator.textual - Java's char is not Text * Fix indent in Map_Spec.enso * Add maps to datapoints in HashCodeTest * Add specialization for maps in HashCodeAnyNode * Add multiLevelAtoms to ValuesGenerator * Provide a workaround for non-linear key inserts * Fix specializations for double and BigInteger * Cosmetics * Add truffle boundaries * Add allowInlining=true to some truffle boundaries. Increases performance a lot. * Increase the size of vectors, and warmup time for Vector.Distinct benchmark * Various small performance fixes. * Fix Geo_Spec tests to accept unsorted Map.to_vector * Implement Map.remove * FIx Visualization tests to accept unsorted Map.to_vector * Treat java.util.Properties as Map * Add truffle boundaries * Invoke polyglot methods on java.util.Properties * Ignore python tests if python lang is missing
2023-01-19 12:33:25 +03:00
[3878]: https://github.com/enso-org/enso/pull/3878
Adds Date, Time_Of_Day and Date_Time support to Excel IO (#3997) - Allow date time inputs from Excel. - Enables disabled test. - Fix for Map.==. - Allow nulls in crosstab name.
2022-12-20 19:12:00 +03:00
[3997]: https://github.com/enso-org/enso/pull/3997
Basic dropdown widget integration (#4013) Implements https://www.pivotaltracker.com/n/projects/2539304/stories/184023445 Added a dropdown widget to graph node for all span tree nodes that have tag values present. When an option is selected, the controller receives a partial expression update, which targets specific crumbs of the expression (similar to how edge endpoint updates work). https://user-images.githubusercontent.com/919491/210219931-8ae418fd-3ac4-44a5-abea-9e670f15cdf9.mp4 # Important Notes Right now the dropdown widget is recreated every time the node is edited, including a dropdown option being selected. This causes it to close every time. I wanted to get around that by diffing span trees, but I wasn't able to do it in useful way. Additionally, current implementation of node input expression view heavily relies on being reinitialized from scratch every time. This led to more necessary changes than I was comfortable with for this task. I believe it will be easier to implement it as part of more complete widget support, especially after dynamic data support, as we will have proper widget type information.
2023-01-11 17:32:25 +03:00
[4013]: https://github.com/enso-org/enso/pull/4013
Align Vector API with design, add some extra functions from AoC (#4026) **Vector** - Adjusted `Vector.sort` to be `Vector.sort order on by`. - Adjusted other sort to use `order` for direction argument. - Added `insert`, `remove`, `index_of` and `last_index_of` to `Vector`. - Added `start` and `if_missing` arguments to `find` on `Vector`, and adjusted default is `Not_Found` error. - Added type checking to `+` on `Vector`. - Altered `first`, `second` and `last` to error with `Index_Out_Of_Bounds` on `Vector`. - Removed `sum`, `exists`, `head`, `init`, `tail`, `rest`, `append`, `prepend` from `Vector`. **Pair** - Added `last`, `any`, `all`, `contains`, `find`, `index_of`, `last_index_of`, `reverse`, `each`, `fold` and `reduce` to `Pair`. - Added `get` to `Pair`. **Range** - Added `first`, `second`, `index_of`, `last_index_of`, `reverse` and `reduce` to `Range`. - Added `at` and `get` to `Range`. - Added `start` and `if_missing` arguments to `find` on `Range`. - Simplified `last` and `length` of `Range`. - Removed `exists` from `Range`. **List** - Added `second`, `find`, `index_of`, `last_index_of`, `reverse` and `reduce` to `Range`. - Added `at` and `get` to `List`. - Removed `exists` from `List`. - Made `all` short-circuit if any fail on `List`. - Altered `is_empty` to not compute the length of `List`. - Altered `first`, `tail`, `head`, `init` and `last` to error with `Index_Out_Of_Bounds` on `List`. **Others** - Added `first`, `second`, `last`, `get` to `Text`. - Added wrapper methods to the Random_Number_Generator so you can get random values more easily. - Adjusted `Aggregate_Column` to operate on the first column by default. - Added `contains_key` to `Map`. - Added ALIAS to `row_count` and `order_by`.
2023-01-12 16:32:24 +03:00
[4026]: https://github.com/enso-org/enso/pull/4026
Implement Distinct for the Database backends (#4027) Implements https://www.pivotaltracker.com/story/show/182307281
2023-01-12 01:46:54 +03:00
[4027]: https://github.com/enso-org/enso/pull/4027
Separate component browser sections for every namespace libraries are imported from (#4044) This PR adds new sections to the component browser section navigator bar. The sections are based on the namespaces from which libraries are imported. Selecting a namespace section from the navigator bar highlights the modules from that namespace. Selecting a module from a different namespace switches the navigator bar indicator to the correct namespace category. The currently selected namespace is also shown as the root of the breadcrumbs. https://user-images.githubusercontent.com/117099775/212144719-2470a99d-8d8c-47ca-ab50-5bac65468090.mp4 For a new project where only the `Standard` namespace exists the only visible change is the breadcrumbs. Adding for example additional modules in the project `src` folder will create them in the `local` namespace, this namespace will show up as a separate navigator section.
2023-01-23 14:57:17 +03:00
[4044]: https://github.com/enso-org/enso/pull/4044
Add `Table.union` to the In-Memory Table. (#4052) Implements https://www.pivotaltracker.com/story/show/183854144
2023-01-17 03:34:57 +03:00
[4052]: https://github.com/enso-org/enso/pull/4052
Add Table.cross_join and Table.zip to In-Memory Table (#4063) Implements https://www.pivotaltracker.com/story/show/184239059
2023-01-23 16:19:52 +03:00
[4063]: https://github.com/enso-org/enso/pull/4063
Update starts_with, ends_with and contains to new API design (#4078) - Updated `Text.starts_with`, `Text.ends_with` and `Text.contains` to new simpler API. - Added a `Case_Sensitivity.Default` and adjusted `Table.distinct` to use it by default. - Fixed a bug with `Data.fetch` on an HTTP error. - Improved SQLite Case Sensitivity control in distinct to use collations.
2023-01-25 14:47:27 +03:00
[4078]: https://github.com/enso-org/enso/pull/4078
Exclude components with a "PRIVATE" tag from the component browser (#4085) This PR removes components from the component browser if they contain a "PRIVATE" tag. Private components from the current module or project are not hidden. ![image](https://user-images.githubusercontent.com/117099775/214826165-9fe2cbee-1559-4602-80e0-5d3ce29d8cef.png)
2023-02-13 12:57:55 +03:00
[4085]: https://github.com/enso-org/enso/pull/4085
New set function, parse a column (#4097) - New `set` function design - takes a `Column` and works with that more easily and supports control of `Set_Mode`. - New simple `parse` API on `Column`. - Separated expression support for `filter` to new `filter_by_expression` on `Table`. - New `compute` function allowing creation of a column from an expression. - Added case sensitivity argument to `Column` based on `starts_with`, `ends_with` and `contains`. - Added case sensitivity argument to `Filter_Condition` for `Starts_With`, `Ends_With`, `Contains` and `Not_Contains`. - Fixed the issue in JS Table visualisation where JavaScript date was incorrectly set. - Some dynamic dropdown expressions - experimenting with ways to use them. - Fixed issue with `.pretty` that wasn't escaping `\`. - Changed default Postgres DB to `postgres`. - Fixed SQLite support for starts_with, ends_with and contains to be consistent (using GLOB not LIKE).
2023-01-31 23:48:16 +03:00
[4097]: https://github.com/enso-org/enso/pull/4097
Introducing Meta.Type (#5956) Fixing #5768 and #5765 and co. Introducing `Meta.Type` and giving it the desired methods. # Important Notes `Type` is no longer a `Meta.Atom`, but it has a dedicated `Meta.Type` representation.
2023-03-17 23:08:18 +03:00
[4115]: https://github.com/enso-org/enso/pull/4115
Ensure Table Visualisation is the Default Visualization for Tables (#4120) Adds a mechanism for the GUI to choose an appropriate default visualization for a newly created node. https://user-images.githubusercontent.com/1428930/216641714-2410d2c9-44d2-45f0-856d-1f995421c94b.mp4 # Important Notes This is a workaround for [missing functionality](https://www.pivotaltracker.com/story/show/184390437) that would take much longer to implement.
2023-02-08 02:23:24 +03:00
[4120]: https://github.com/enso-org/enso/pull/4120
Roll back last VCS snapshot (#4050) Fixes #5001 This PR implements reverting the current project state to the last state saved into the VCS. This action is performed on `ctrl+r`. https://user-images.githubusercontent.com/117099775/216645556-1bf34ee7-fdb4-4833-bcad-670d688a3199.mp4 # Important Notes * Currently on `vcs/restore` all expressions are invalidated and all nodes are re-executed. This is tracked in [task](https://www.pivotaltracker.com/n/projects/2539304/stories/184368950).
2023-02-16 21:14:34 +03:00
[4050]: https://github.com/enso-org/enso/pull/4050
Dynamic dropdown support (#4072) Implementation of https://www.pivotaltracker.com/story/show/184012743 https://user-images.githubusercontent.com/919491/214082311-cf49e43c-1d1f-4654-903c-a4224cd954d8.mp4 This is also a step towards more general widget support. The widget metadata is queried using `Meta.get_annotation` method through a dedicated visualization. For now only `Single_Choice` case is handled, and always all suggestions are is returned. # Important Notes There are limitations as to which node segments receive a widget. Only chain method calls are supported now (`thing.method` syntax), and only outside of lambda scope. Widgets in lambdas will require support for visualisations of lambda subexpressions, which is currently missing in the engine. The IDE technically tries to place the widgets there, but the data never arrives. It should work once the engine support is added. This PR includes a mock for `Meta.get_annotation` call that only supports `Table.at` method. Real implementation is a separate task that is already in progress.
2023-02-04 03:50:24 +03:00
[4072]: https://github.com/enso-org/enso/pull/4072
Add a shortcut to toggle the visibility of private components in the component browser (#5582) Closes #4962 This PR adds the `cmd+alt+p` shortcut to toggle the visibility of components with a "PRIVATE" tag in the component browser. The default is to have these private components hidden. https://user-images.githubusercontent.com/117099775/219106357-0b14a5b5-404f-44dd-b30c-5389054683a7.mp4
2023-02-21 00:24:51 +03:00
[5582]: https://github.com/enso-org/enso/pull/5582
Improve searching of component browser entries (#5645) Closes #5102 This PR improves searching entries in the component browser. Now the searcher input is also matched to the code that a component would generate, and the best match of the two is used for filtering and sorting the components in the component browser. https://user-images.githubusercontent.com/117099775/219328904-c7a067d5-4998-4ee5-8475-d4974cd7bff5.mp4 #### Entry name formatting Additionally, the component entry's displayed name format is changed to show the method's name first, followed by the type name in parentheses. This formatting fits better in the narrow columns of the component browser.
2023-02-17 02:21:37 +03:00
[5645]: https://github.com/enso-org/enso/pull/5645
Remove `Column` type from Aggregate_Column, simplify Column_Selector, some new `File_Format`s (#5646) - Updated `Widget.Vector_Editor` ready for use by IDE team. - Added `get` to `Row` to make API more aligned. - Added `first_column`, `second_column` and `last_column` to `Table` APIs. - Adjusted `Column_Selector` and associated methods to have simpler API. - Removed `Column` from `Aggregate_Column` constructors. - Added new `Excel_Workbook` type and added to `Excel_Section`. - Added new `SQLiteFormatSPI` and `SQLite_Format`. - Added new `IamgeFormatSPI` and `Image_Format`.
2023-02-16 18:15:49 +03:00
[5646]: https://github.com/enso-org/enso/pull/5646
Support widgets and placeholders in more complex expressions (#5656) Implements https://github.com/enso-org/enso/issues/5032 Added support for widgets in infix expressions (right now only used for file paths) <img width="306" alt="image" src="https://user-images.githubusercontent.com/919491/218736181-98965cd4-2a8e-4f7a-bbf8-ab302ac5b22c.png"> Widgets and placeholders are handled for all chained methods within a node <img width="292" alt="image" src="https://user-images.githubusercontent.com/919491/218736249-a0190115-623e-4e66-aff4-90eb2a50685d.png"> The qualified method call convention and static methods no longer confuse the argument placeholders <img width="374" alt="image" src="https://user-images.githubusercontent.com/919491/218736628-24073f5c-0512-4b37-a271-0248bc954802.png"> Type constructor expressions now receive placeholder arguments. The placeholders work on nested expressions within a node. <img width="405" alt="image" src="https://user-images.githubusercontent.com/919491/218737379-b53ff125-3910-48f3-bb9f-a0e7b1684ab9.png">
2023-02-20 09:39:39 +03:00
[5656]: https://github.com/enso-org/enso/pull/5656
Update `rename_columns` to new API design, add `first_row`, `second_row` and `last_row` functions to the table. (#5719) - Updates the `rename_columns` API. - Add `first_row`, `second_row` and `last_row` to the Table types. - New option for reading only last row of ResultSet.
2023-02-23 22:42:45 +03:00
[5678]: https://github.com/enso-org/enso/pull/5678
Wip/gmt/match find only text (#5721) Rename is_match + match to match + find (respectively), and remove all non-regexp functionality. Regexp flags and Match_Mode are also no longer supported by these methods.
2023-02-23 12:47:10 +03:00
[5679]: https://github.com/enso-org/enso/pull/5679
File.parent can return Nothing (#5699) `File.parent` can be `Nothing`
2023-02-20 22:13:56 +03:00
[5699]: https://github.com/enso-org/enso/pull/5699
Update `rename_columns` to new API design, add `first_row`, `second_row` and `last_row` functions to the table. (#5719) - Updates the `rename_columns` API. - Add `first_row`, `second_row` and `last_row` to the Table types. - New option for reading only last row of ResultSet.
2023-02-23 22:42:45 +03:00
[5719]: https://github.com/enso-org/enso/pull/5719
Wip/gmt/match find only text (#5721) Rename is_match + match to match + find (respectively), and remove all non-regexp functionality. Regexp flags and Match_Mode are also no longer supported by these methods.
2023-02-23 12:47:10 +03:00
[5721]: https://github.com/enso-org/enso/pull/5721
Fix missing visualization preview in CB (#5757) Closes #5639 This PR fixes a regression introduced in #4120, due to which new nodes that were being edited had an empty visualization preview. Now newly created visualization containers do get a default visualization set even before the visualization's input type is set. https://user-images.githubusercontent.com/117099775/221256294-c87a50da-c8b0-4f00-bf84-f5ae551fca72.mp4
2023-02-27 23:10:23 +03:00
[5757]: https://github.com/enso-org/enso/pull/5757
Introducing Meta.Type (#5956) Fixing #5768 and #5765 and co. Introducing `Meta.Type` and giving it the desired methods. # Important Notes `Type` is no longer a `Meta.Atom`, but it has a dedicated `Meta.Type` representation.
2023-03-17 23:08:18 +03:00
[5768]: https://github.com/enso-org/enso/pull/5768
Named arguments support in IDE (#5774) Added support for named arguments in IDE. https://user-images.githubusercontent.com/919491/223681303-4c716639-d06e-4e33-aa22-6ebca2801b01.mp4 Named arguments are now recognized in node expressions. The function argument placeholders are rendered around series of named arguments. Insertion and deletion of arguments either by connection dragging or by widget selection will cause arguments around to be rewritten into appropriate form, such that the meaning of the expression doesn't change. We no longer need to introduce any wildcards (`_`) in argument positions when editing an argument list of a resolved method. ![image](https://user-images.githubusercontent.com/919491/223682460-143eb6d7-5ac9-4732-9520-71216cbbe58f.png) For unresolved function calls, the old behaviour remains, as we don't have data about argument names or their desired order.
2023-03-10 00:23:25 +03:00
[5774]: https://github.com/enso-org/enso/pull/5774
Regex.Compile using Truffle Regex, update find, match and match_all (#5785)
2023-03-11 00:49:50 +03:00
[5779]: https://github.com/enso-org/enso/pull/5779
[5785]: https://github.com/enso-org/enso/pull/5785
Cognito auth 2/7 - add authorization app (#5798) 2nd PR for IDE/Cloud authorization with cognito. This PR introduces boilerplate react app + some amplify code to fetch the access token + username of the currently logged in user, if they are already authenticated. Registration + Login + Set Username + Forgot Password flows are to be added in next PRs to keep the changes reviewable.
2023-03-15 14:54:16 +03:00
[5798]: https://github.com/enso-org/enso/pull/5798
Regex.Compile using Truffle Regex, update find, match and match_all (#5785)
2023-03-11 00:49:50 +03:00
[5802]: https://github.com/enso-org/enso/pull/5802
Review generated Column names (#5850) Closes #5583 and closes #5157
2023-03-10 22:07:58 +03:00
[5850]: https://github.com/enso-org/enso/pull/5850
Fix `cross_tab` column naming edge cases, add `fill_empty` (#5863) Closes #5151 and adds some additional tests for `cross_tab` that verify duplicated and invalid names. I decided that for empty or `Nothing` names, instead of replacing them with `Column` and implicitly losing connection with the value that was in the column, we should just error on such values. To make handling of these easier, `fill_empty` was added allowing to easily replace the empty values with something else. Also, `{is,fill}_missing` was renamed to `{is,fill}_nothing` to align with `Filter_Condition.Is_Nothing`.
2023-03-11 14:58:54 +03:00
[5863]: https://github.com/enso-org/enso/pull/5863
New documentation parser (#5917) Implement new Enso documentation parser; remove old Scala Enso parser. Performance: Total time parsing documentation is now ~2ms. # Important Notes - Doc parsing is now done only in the frontend. - Some engine tests had never been switched to the new parser. We should investigate tests that don't pass after the switch: #5894. - The option to run the old searcher has been removed, as it is obsolete and was already broken before this (see #5909). - Some interfaces used only by the old searcher have been removed.
2023-03-15 18:43:51 +03:00
[5917]: https://github.com/enso-org/enso/pull/5917
support custom widget entry labels (#5705) Implements #5640 and #5650 It made sense for me to implement those two together, as I wanted to make sure that the necessary widget API changes will support custom entry values for both dynamic and static data. - Added support for custom dropdown labels defined on the method annotations - Added shortening of static dropdown values, which resolves | dynamic dropdown - custom labels | static dropdown - automatic shortening | |-|-| |![image](https://user-images.githubusercontent.com/919491/220117241-8682736e-d750-4eeb-b9bb-cd6cfce42356.png)|![image](https://user-images.githubusercontent.com/919491/220117412-05ad7f4a-3ccf-468b-a976-c52395a497e2.png)| # Important Notes During implementation I had multiple data update order issues caused by FRP network forming a diamond shape. Two inputs that are often updated together were combined with `all` combinator, and that was further fed into the dropdown. This caused two updates to propagate through the whole network, and one of them was immediately outdated. To fix this and similar future scenarios, I've added an `next_tick` FRP node. It buffers the incoming events until the next browser microtask, preserving only the last received event. Currently if it is called inside a `requestAnimationFrame` callback, the effects of that processing will only be rendered in the next frame. Later this can be mitigated by delaying the rendering logic until the microtask queue is empty.
2023-03-17 13:06:32 +03:00
[5705]: https://github.com/enso-org/enso/pull/5705
Implement Regular Expression replace and update `Text.replace` to the new API (#5959) Re-implement replace on top of Truffle regex.
2023-03-28 09:13:12 +03:00
[5959]: https://github.com/enso-org/enso/pull/5959
Proper implementation of Value Types in Table (#6073) This is the first part of the #5158 umbrella task. It closes #5158, follow-up tasks are listed as a comment in the issue. - Updates all prototype methods dealing with `Value_Type` with a proper implementation. - Adds a more precise mapping from in-memory storage to `Value_Type`. - Adds a dialect-dependent mapping between `SQL_Type` and `Value_Type`. - Removes obsolete methods and constants on `SQL_Type` that were not portable. - Ensures that in the Database backend, operation results are computed based on what the Database is meaning to return (by asking the Database about expected types of each operation). - But also ensures that the result types are sane. - While SQLite does not officially support a BOOLEAN affinity, we add a set of type overrides to our operations to ensure that Boolean operations will return Boolean values and will not be changed to integers as SQLite would suggest. - Some methods in SQLite fallback to a NUMERIC affinity unnecessarily, so stuff like `max(text, text)` will keep the `text` type instead of falling back to numeric as SQLite would suggest. - Adds ability to use custom fetch / builder logic for various types, so that we can support vendor specific types (for example, Postgres dates). # Important Notes - There are some TODOs left in the code. I'm still aligning follow-up tasks - once done I will try to add references to relevant tasks in them.
2023-03-31 19:16:18 +03:00
[6073]: https://github.com/enso-org/enso/pull/6073
#5123 Text.tokenize (#6150) Implement Text.tokenize.
2023-04-03 23:13:49 +03:00
[6116]: https://github.com/enso-org/enso/pull/6116
[6150]: https://github.com/enso-org/enso/pull/6150
Date/time support for Postgres. Year/month/day operations on Columns. (#6153) Closes #6115
2023-03-31 21:37:04 +03:00
[6153]: https://github.com/enso-org/enso/pull/6153
Update `Text.split` to take a `Vector Text` parameter (#6156) Allows you to pass a vector of delimiters to `split`.
2023-04-04 17:44:47 +03:00
[6156]: https://github.com/enso-org/enso/pull/6156
Add Warning methods onto Any to make working with them easier. (#6176) Adds `has_warnings`, `remove_warnings` and `throw_on_warning` extension methods.
2023-04-12 18:08:01 +03:00
[6176]: https://github.com/enso-org/enso/pull/6176
Implement `Table.union` for Database backend (#6204) Closes #5235
2023-04-06 11:40:34 +03:00
[6204]: https://github.com/enso-org/enso/pull/6204
Project Sharing (#6077) Enso will now associate with two file extensions: * `.enso` — Enso source file. * If the source file belongs to a project under the Project Manager-managed directory, it will be opened. * If the source file belongs to a project located elsewhere, it will be imported into the PM-managed directory and opened; * Otherwise, opening the `.enseo` file will fail. (e.g., loose source file without any project) * `.enso-project` — Enso project bundle, i.e., `tar.gz` archive containing a compressed Enso project directory. * it will be imported under the PM-managed directory; a unique directory name shall be generated if needed. ### Important Notes On Windows, the NSIS installer is expected to handle the file associations. On macOS, the file associations are expected to be set up after the first time Enso is started, On Linux, the file associations are not supported yet.
2023-04-06 16:26:37 +03:00
[6077]: https://github.com/enso-org/enso/pull/6077
Consolidate Vector and Array methods (#6218) Fixes #5011 by making sure the same methods that are on `Vector` are also available on `Array`.
2023-04-11 19:20:11 +03:00
[6218]: https://github.com/enso-org/enso/pull/6218
Add split and tokenize to the Table. (#6233) Implement split and tokenize for tables.
2023-04-14 19:03:02 +03:00
[6233]: https://github.com/enso-org/enso/pull/6233
Add `replace`, `trim` to Column. Better number parsing. (#6253) - Add `replace` with same syntax as on `Text` to an in-memory `Column`. - Add `trim` with same syntax as on `Text` to an in-memory `Column`. - Add `trim` to in-database `Column`. - Added `is_supported` to dialects and exposed the dialect consistently on the `Connection`. - Add `write_table` support to `JSON_File` allowing `Table.write` to write JSON. - Updated the parsing for integers and decimals: - Support for currency symbols. - Support for brackets for negative numbers. - Automatic detection of decimal points and thousand separators. - Tighter rules for scientific and thousand separated numbers. - Remove `replace_text` from `Table`. - Remove `write_json` from `Table`.
2023-04-20 19:04:59 +03:00
[6253]: https://github.com/enso-org/enso/pull/6253
Add Table.parse_text_to_table to convert Text to a Table. (#6294)
2023-04-21 20:43:19 +03:00
[6294]: https://github.com/enso-org/enso/pull/6294
5127 Add Table.parse_to_columns to parse a single column to a set of columns. (#6383) Implement Table.parse_to_columns
2023-04-24 18:21:38 +03:00
[6383]: https://github.com/enso-org/enso/pull/6383
Add parse extensions to Text type. #6330 (#6404) Add type-specific parse stubs to Text, e.g.: Text.parse_json self -> Json = Text.parse_url self -> Url = Text.parse_number self -> Number =
2023-04-26 18:37:09 +03:00
[6404]: https://github.com/enso-org/enso/pull/6404
Widgets integrated with graph nodes (#6347) Rewrites node input component. Now the input is composed of multiple widget components arranged in a tree of views with automatic layout. That allows creating complex UI elements on top of the node itself, and further widget positions will be automatically adapted to that. The tree roughly follow the span tree, as it is built by consuming its nodes and eagerly creating widgets from them. The tree is rebuilt every time the expression changes, but that rebuild process reuses as much previously created widgets as possible, and only updates their configuration as needed. Each widget type can have its own configuration options that can be passed to it from the parent, or assigned based on configuration received from the language server. <img width="773" alt="image" src="https://user-images.githubusercontent.com/919491/233439310-9c39ea88-19bc-43da-9baf-1bb176e2724e.png"> # Important Notes For now, all span-tree updates are sent over to the shared Frp endpoint of the whole tree, so there is no mechanism for intercepting them by the parent widgets. One idea would be to use existing bubbling/capturing events on widget display objects for that purpose, but I think existing implementation is simpler and more convenient, and we can always easily change that if we have a use for it. There are some issues with performance due to much more display objects being created on the graph. Expect it to be a little worse, especially at initialization time.
2023-04-26 22:37:54 +03:00
[6347]: https://github.com/enso-org/enso/pull/6347
Create database table from memory (#6429)
2023-04-27 23:06:17 +03:00
[6429]: https://github.com/enso-org/enso/pull/6429
Add Execution Context control to Text.write (#6459) - Adjusted `Context.is_enabled` to support default argument (moved built in so can have defaults). - Made `environment` case-insensitive. - Bug fix for play button. - Short hand to execute within an enabled context. - Forbid file writing if the Output context is disabled with a `Forbidden_Operation` error. - Add temporary file support via `File.create_temporary_file` which is deleted on exit of JVM. - Execution Context first pass in `Text.write`. - Added dry run warning. - Writes to a temporary file if disabled. - Created a `DryRunFileManager` which will create and manage the temporary files. - Added `format` dropdown to `File.read` and `Data.read`. - Renamed `JSON_File` to `JSON_Format` to be consistent. (still to unit test).
2023-04-29 11:39:18 +03:00
[6459]: https://github.com/enso-org/enso/pull/6459
Implement `create_database_table` for Database Table (#6467) Closes #6327
2023-05-02 17:01:44 +03:00
[6467]: https://github.com/enso-org/enso/pull/6467
Add format to the in-memory Column (#6538) Add format to the in-memory Column # Important Notes Also updates .format in date types. Some rearrangement of date formatting builtins / Java libraries.
2023-05-09 11:47:40 +03:00
[6538]: https://github.com/enso-org/enso/pull/6538
"at_least_one" flag for tokenize_to_rows (#6539) Add "at_least_one" flag for tokenize_to_rows.
2023-05-06 09:22:09 +03:00
[6539]: https://github.com/enso-org/enso/pull/6539
Separating Redshift connector from `Database` library into a new `AWS` library (#6550) Related to #5777
2023-05-04 20:36:51 +03:00
[6550]: https://github.com/enso-org/enso/pull/6550
Add `Date_Range` (#6621) Closes #6543
2023-05-11 19:03:02 +03:00
[6621]: https://github.com/enso-org/enso/pull/6621
Implement `cast` for Table and Column (#6711) Closes #6112
2023-05-19 13:00:20 +03:00
[6711]: https://github.com/enso-org/enso/pull/6711
Decimal/Integer .round and .int #6654 (#6743)
2023-05-19 22:23:17 +03:00
[6743]: https://github.com/enso-org/enso/pull/6743
Add rounding functions to the Column type (#6817)
2023-06-01 23:06:23 +03:00
[6817]: https://github.com/enso-org/enso/pull/6817
Execution control for Table.write and various widget tweaks... (#6835) - Adds execution control to `Table.write`. - Refactored the `Text.write` to make part reusable. - Tidied up some legacy mess in tests. - Add easier flow to go from `Text` to an `URI` to fetching data. - Add decode functions to `Response` and `Response_Body`. - Fix issue with 0 length regex matches (using same as Python and .Net approach). - Add various ALIAS entries to make function discovery easier. - Sort a lot of drop down and vector editors out (including switch to fully qualified names).
2023-06-02 01:10:03 +03:00
[6835]: https://github.com/enso-org/enso/pull/6835
Implement `Table.add_row_number` (#6890) Closes #5227 # Important Notes - This lays first steps towards #6292 - we get pure Enso variants of MultiValueKey. - Another part refactors `LongStorage` into `AbstractLongStorage` allowing it to provide alternative implementations of the underlying storage, in our case `LongRangeStorage` generating the values ad-hoc and `LongConstantStorage` - currently unused but in the future it can be adapted to support constant columns (once we implement similar facilities for other types).
2023-06-02 13:13:13 +03:00
[6890]: https://github.com/enso-org/enso/pull/6890
Handle some edge cases in rounding (inexact representations and overflows) (#6922)
2023-06-05 20:21:13 +03:00
[6922]: https://github.com/enso-org/enso/pull/6922
Refactor `create_database_table` into `Connection.create_table` and `select_into_database_table`, implement `Set`. (#6925) First part for #6498 - refactoring of the upload infrastructure, in preparation for `update_database_table`. Implemented a `Set` data structure which was long needed. The APIs are added and an initial implementation is created, but it is not complete - but it has grown significantly already so the remaining implementation will be done as a separate PR. Adds some basic ability for a function to ensure that it is only executed from within a transaction.
2023-06-06 13:36:05 +03:00
[6925]: https://github.com/enso-org/enso/pull/6925
Reimplement Column.truncate, .ceil, and .floor as vectorized Java ops (#6941) Reimplement these in Java. Benchmarks: Before: Column.truncate floats average: 124.4ms Column.ceil floats average: 121.47ms Column.floor floats average: 120.18ms Column.truncate ints average: 124.78ms Column.ceil ints average: 120.41ms Column.floor ints average: 102.35ms After (boxed): Column.truncate floats average: 3.75ms Column.ceil floats average: 2.25ms Column.floor floats average: 1.89ms Column.truncate ints average: 2ms Column.ceil ints average: 1.77ms Column.floor ints average: 1.74ms After (unboxed): Column.truncate floats average: 3.32ms Column.ceil floats average: 2.15ms Column.floor floats average: 1.69ms Column.truncate ints average: 1.74ms Column.ceil ints average: 1.61ms Column.floor ints average: 1.99ms
2023-06-06 21:07:12 +03:00
[6941]: https://github.com/enso-org/enso/pull/6941
Implement addition and subtraction for Date_Period and Time_Period (#6956) Date.+ should allow Date_Period, Time_Of_Day.+ should allow Time_Period and Date_TIme.+ should allow both. Same for subtraction.
2023-06-07 15:46:19 +03:00
[6956]: https://github.com/enso-org/enso/pull/6956
First part of AWS S3 API, various small fixes. (#6973) - Add type detection for `Mixed` columns when calling column functions. - Excel uses column name for missing headers. - Add aliases for parse functions on text. - Adjust `Date`, `Time_Of_Day` and `Date_Time` parse functions to not take `Nothing` anymore and provide dropdowns. - Removed built-in parses. - All support Locale. - Add support for missing day or year for parsing a Date. - All will trim values automatically. - Added ability to list AWS profiles. - Added ability to list S3 buckets. - Workaround for Table.aggregate so default item added works.
2023-06-15 19:20:13 +03:00
[6973]: https://github.com/enso-org/enso/pull/6973
Improving widgets and other minor tweaks. (#7052) - Removed `module` argument from `enso_project` (new `Project_Description.new` API). - Removed the custom option from date and time parse/format dropdowns. - The `format` dropdown uses the value to create the dropdown. (Screenshot below) - Removed `StorageType` coalescing rules and replaced them with simpler logic in `ObjectStorage`. - Update signature for `add_row_number` and add aliases.
2023-06-19 22:03:36 +03:00
[7035]: https://github.com/enso-org/enso/pull/7035
[7052]: https://github.com/enso-org/enso/pull/7052
Colorful Histograms (#3153)
2021-11-18 17:17:38 +03:00
Implement conversions (#180312665) (#3227) * Implement conversions start wip branch for conversion methods for collaborating with marcin add conversions to MethodDispatchLibrary (wip) start MethodDispatchLibrary implementations conversions for atoms and functions Implement a bunch of missing conversion lookups final bug fixes for merged methoddispatchlibrary implementations UnresolvedConversion.resolveFor progress on invokeConversion start extracting constructors (still not working) fix a bug add some initial conversion tests fix a bug in qualified name resolution, test conversions accross modules implement error reporting, discover a ton of ignored errors... start fixing errors that we exposed in the standard library fix remaining standard lib type errors not caused by the inability to parse type signatures for operators TODO: fix type signatures for operators. all of them are broken fix type signature parsing for operators test cases for meta & polyglot play nice with polyglot start pretending unresolved conversions are unresolved symbols treat UnresolvedConversons as UnresolvedSymbols in enso user land * update RELEASES.md * disable test error about from conversions being tail calls. (pivotal issue #181113110) * add changelog entry * fix OverloadsResolutionTest * fix MethodDefinitionsTest * fix DataflowAnalysisTest * the field name for a from conversion must be 'that'. Fix remaining tests that aren't ExpressionUpdates vs. ExecutionUpdate behavioral changes * fix ModuleThisToHereTest * feat: suppress compilation errors from Builtins * Revert "feat: suppress compilation errors from Builtins" This reverts commit 63d069bd4f059baad76b7b421c4a1330ea5ffea5. * fix tests * fix: formatting Co-authored-by: Dmitry Bushev <bushevdv@gmail.com> Co-authored-by: Marcin Kostrzewa <marckostrzewa@gmail.com>
2022-02-06 12:02:09 +03:00
#### Enso Compiler
- [Added overloaded `from` conversions.][3227]
Upgrade Truffle and Graal to Version 21.3.0 (#3258)
2022-02-11 19:05:13 +03:00
- [Upgraded to Graal VM 21.3.0][3258]
Decorate values with arbitrary warnings (#3248)
2022-03-09 18:40:02 +03:00
- [Added the ability to decorate values with warnings.][3248]
Initialize AtomConstructor's fields via local vars (#3330) The mechanism follows a similar approach to what is being in functions with default arguments. Additionally since InstantiateAtomNode wasn't a subtype of EnsoRootNode it couldn't be used in the application, which was the primary reason for issue #181449213. Alternatively InstantiateAtomNode could have been enhanced to extend EnsoRootNode rather than RootNode to carry scope info but the former seemed simpler. See test cases for previously crashing and invalid cases.
2022-03-21 12:15:14 +03:00
- [Fixed issues related to constructors' default arguments][3330]
Fix resource management in ModuleCache (#3367) PR fixes an issue when compiler crashes while trying to load an incompatible `IR` cache.
2022-03-29 16:47:03 +03:00
- [Fixed compiler issue related to module cache.][3367]
Always call defaulted atom arguments (#3358) Solves the issue of defaulted args not being called in atoms. Doesn't solve the more general function issue.
2022-04-08 11:21:59 +03:00
- [Fixed execution of defaulted arguments of Atom Constructors][3358]
Improved polyglot Date support (#3559) Significantly improves the polyglot Date support (as introduced by #3374). It enhances the `Date_Spec` to run it in four flavors: - with Enso Date (as of now) - with JavaScript Date - with JavaScript Date wrapped in (JavaScript) array - with Java LocalDate allocated directly The code is then improved by necessary modifications to make the `Date_Spec` pass. # Important Notes James has requested in [#181755990](https://www.pivotaltracker.com/n/projects/2539304/stories/181755990) - e.g. _Review and improve InMemory Table support for Dates, Times, DateTimes, BigIntegers_ the following program to work: ``` foreign js dateArr = """ return [1, new Date(), 7] main = IO.println <| (dateArr.at 1).week_of_year ``` the program works with here in provided changes and prints `27` as of today. @jdunkerley has provided tests for proper behavior of date in `Table` and `Column`. Those tests are working as of [f16d07e](https://github.com/enso-org/enso/pull/3559/commits/f16d07e640c12721eb329a797a19c7b46bbf3fbc). One just needs to accept `List<Value>` and then query `Value` for `isDate()` when needed. Last round of changes is related to **exception handling**. https://github.com/enso-org/enso/pull/3559/commits/8b686b12bdc1113e07ff37bc780df960aae34039 makes sure `makePolyglotError` accepts only polyglot values. Then it wraps plain Java exceptions into `WrapPlainException` with `has_type` method - https://github.com/enso-org/enso/pull/3559/commits/60da5e70ed58db55e00bf82f57f47063a6d1e587 - the remaining changes in the PR are only trying to get all tests working in the new setup. The support for `Time` isn't part of this PR yet.
2022-07-21 09:32:40 +03:00
- [Converting Enso Date to java.time.LocalDate and back][3559]
Avoid whole source reparsing when the IDE performs a simple edit (#3508) Co-authored-by: Dmitry Bushev <bushevdv@gmail.com> Co-authored-by: Hubert Plociniczak <hubert.plociniczak@gmail.com>
2022-06-16 17:02:57 +03:00
- [Incremental Reparsing of a Simple Edits][3508]
Automatically force all-defaulted functions (#3414) This changes the interpreter to treat functions with all-defaulted args as thunks. Seems to have no performance impact in compiled code.
2022-04-27 20:57:00 +03:00
- [Functions with all-defaulted arguments now execute automatically][3414]
Sum type info in suggestions DB (#3422) A draft of simple changes to the compiler to expose sum type information. Doesn't break the stdlib & at the same time allows for dropdowns. This is still broken, for example it doesn't handle exporting/importing types, only ones defined in the same module as the signature. Still, seems like a step in the right direction – please provide feedback. # Important Notes I've decided to make the variant info part of the type, not the argument – it is a property of the type logically. Also, I've pushed it as far as I'm comfortable – i.e. to the `SuggestionHandler` – I have no idea if this is enough to show in IDE? cc @4e6
2022-05-05 19:05:22 +03:00
- [Provide `tagValues` for function arguments in the language server][3422]
Delay conversion of Truffle function body nodes until the function is invoked (#3429) Most of the functions in the standard library aren't gonna be invoked during particular program execution. It makes no sense to build their Truffle AST for the functions that are not executing. Let's delay the construction of the tree until a function is first executed.
2022-05-05 13:53:49 +03:00
- [Delay construction of Truffle nodes to speed initialization][3429]
Frgaal integration in sbt (#3421) * Initial integration with Frgaal in sbt Half-working since it chokes on generated classes from annotation processor. * Replace AutoService with ServiceProvider For reasons unknown AutoService would fail to initialize and fail to generate required builtin method classes. Hidden error message is not particularly revealing on the reason for that: ``` [error] error: Bad service configuration file, or exception thrown while constructing Processor object: javax.annotation.processing.Processor: Provider com.google.auto.service.processor.AutoServiceProcessor could not be instantiated ``` The sample records is only to demonstrate that we can now use newer Java features. * Cleanup + fix benchmark compilation Bench requires jmh classes which are not available because we obviously had to limit `java.base` modules to get Frgaal to work nicely. For now, we default to good ol' javac for Benchmarks. Limiting Frgaal to runtime for now, if it plays nicely, we can expand it to other projects. * Update CHANGELOG * Remove dummy record class * Update licenses * New line * PR review * Update legal review Co-authored-by: Radosław Waśko <radoslaw.wasko@enso.org>
2022-05-04 22:18:40 +03:00
- [Frgaal compiler integration to allow for latest Java constructs][3421]
Debug Enso language in ChromeDev tools with --inspect option (#3432) Finally this pull request proposes `--inspect` option to allow [debugging of `.enso`](https://github.com/enso-org/enso/blob/e948f2535f71249daed647181324746613081d29/docs/debugger/README.md) in Chrome Developer Tools: ```bash enso$ ./built-distribution/enso-engine-0.0.0-dev-linux-amd64/enso-0.0.0-dev/bin/enso --inspect --run ./test/Tests/src/Data/Numbers_Spec.enso Debugger listening on ws://127.0.0.1:9229/Wugyrg9Nm4OUL9YhzdcElmLft71ayZW3LMUPCdPyNAY For help, see: https://www.graalvm.org/tools/chrome-debugger E.g. in Chrome open: devtools://devtools/bundled/js_app.html?ws=127.0.0.1:9229/Wugyrg9Nm4OUL9YhzdcElmLft71ayZW3LMUPCdPyNAY ``` copy the printed URL into chrome browser and you should see: ![obrazek](https://user-images.githubusercontent.com/26887752/167235327-8ad15fb2-96d4-4a0c-9e31-ed67ab46578b.png) One can also debug the `.enso` files in NetBeans or [VS Code with Apache Language Server extension](https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Extension+for+Visual+Studio+Code) just pass in special JVM arguments: ```bash enso$ JAVA_OPTS=-agentlib:jdwp=transport=dt_socket,server=y,address=8000 ./built-distribution/enso-engine-0.0.0-dev-linux-amd64/enso-0.0.0-dev/bin/enso --run ./test/Tests/src/Data/Numbers_Spec.enso Listening for transport dt_socket at address: 8000 ``` and then _Debug/Attach Debugger_. Once connected choose the _Toggle Pause in GraalVM Script_ button in the toolbar (the "G" button): ![obrazek](https://user-images.githubusercontent.com/26887752/167235598-98266c7e-beb5-406b-adc6-8167b3d1b453.png) and your execution shall stop on the next `.enso` line of code. This mode allows to debug both - the Enso code as well as Java code. Originally started as an attempt to write test in Java: * test written in Java * support for JUnit in `build.sbt` * compile Java with `-g` - so it can be debugged * Implementation of `StatementNode` - only gets created when `materialize` request gets to `BlockNode`
2022-05-10 11:55:08 +03:00
- [Support for Chrome developer tools --inspect option][3432]
Move Builtin Types and Methods to stdlib (#3363) This PR replaces hard-coded `@Builtin_Method` and `@Builtin_Type` nodes in Builtins with an automated solution that a) collects metadata from such annotations b) generates `BuiltinTypes` c) registers builtin methods with corresponding constructors. The main differences are: 1) The owner of the builtin method does not necessarily have to be a builtin type 2) You can now mix regular methods and builtin ones in stdlib 3) No need to keep track of builtin methods and types in various places and register them by hand (a source of many typos or omissions as it found during the process of this PR) Related to #181497846 Benchmarks also execute within the margin of error. ### Important Notes The PR got a bit large over time as I was moving various builtin types and finding various corner cases. Most of the changes however are rather simple c&p from Builtins.enso to the corresponding stdlib module. Here is the list of the most crucial updates: - `engine/runtime/src/main/java/org/enso/interpreter/runtime/builtin/Builtins.java` - the core of the changes. We no longer register individual builtin constructors and their methods by hand. Instead, the information about those is read from 2 metadata files generated by annotation processors. When the builtin method is encountered in stdlib, we do not ignore the method. Instead we lookup it up in the list of registered functions (see `getBuiltinFunction` and `IrToTruffle`) - `engine/runtime/src/main/java/org/enso/interpreter/runtime/callable/atom/AtomConstructor.java` has now information whether it corresponds to the builtin type or not. - `engine/runtime/src/main/scala/org/enso/compiler/codegen/RuntimeStubsGenerator.scala` - when runtime stubs generator encounters a builtin type, based on the @Builtin_Type annotation, it looks up an existing constructor for it and registers it in the provided scope, rather than creating a new one. The scope of the constructor is also changed to the one coming from stdlib, while ensuring that synthetic methods (for fields) also get assigned correctly - `engine/runtime/src/main/scala/org/enso/compiler/codegen/IrToTruffle.scala` - when a builtin method is encountered in stdlib we don't generate a new function node for it, instead we look it up in the list of registered builtin methods. Note that Integer and Number present a bit of a challenge because they list a whole bunch of methods that don't have a corresponding method (instead delegating to small/big integer implementations). During the translation new atom constructors get initialized but we don't want to do it for builtins which have gone through the process earlier, hence the exception - `lib/scala/interpreter-dsl/src/main/java/org/enso/interpreter/dsl/MethodProcessor.java` - @Builtin_Method processor not only generates the actual code fpr nodes but also collects and writes the info about them (name, class, params) to a metadata file that is read during builtins initialization - `lib/scala/interpreter-dsl/src/main/java/org/enso/interpreter/dsl/MethodProcessor.java` - @Builtin_Method processor no longer generates only (root) nodes but also collects and writes the info about them (name, class, params) to a metadata file that is read during builtins initialization - `lib/scala/interpreter-dsl/src/main/java/org/enso/interpreter/dsl/TypeProcessor.java` - Similar to MethodProcessor but handles @Builtin_Type annotations. It doesn't, **yet**, generate any builtin objects. It also collects the names, as present in stdlib, if any, so that we can generate the names automatically (see generated `types/ConstantsGen.java`) - `engine/runtime/src/main/java/org/enso/interpreter/node/expression/builtin` - various classes annotated with @BuiltinType to ensure that the atom constructor is always properly registered for the builitn. Note that in order to support types fields in those, annotation takes optional `params` parameter (comma separated). - `engine/runtime/src/bench/scala/org/enso/interpreter/bench/fixtures/semantic/AtomFixtures.scala` - drop manual creation of test list which seemed to be a relict of the old design
2022-05-05 21:18:06 +03:00
- [Move Builtin Types and Methods definitions to stdlib][3363]
Generate BuiltinMethods from simple method and constructor signatures (#3444) A low-hanging fruit where we can automate the generation of many @BuiltinMethod nodes simply from the runtime's methods signatures. This change introduces another annotation, @Builtin, to distinguish from @BuiltinType and @BuiltinMethod processing. @Builtin processing will always be the first stage of processing and its output will be fed to the latter. Note that the return type of Array.length() is changed from `int` to `long` because we probably don't want to add a ton of specializations for the former (see comparator nodes for details) and it is fine to cast it in a small number of places. Progress is visible in the number of deleted hardcoded classes. This is an incremental step towards #181499077. # Important Notes This process does not attempt to cover all cases. Not yet, at least. We only handle simple methods and constructors (see removed `Array` boilerplate methods).
2022-05-12 11:42:00 +03:00
- [Reduce boilerplate by generating BuiltinMethod nodes from simple method
signatures][3444]
Part 2 of system for builtin objects (#3454) This is the 2nd part of DSL improvements that allow us to generate a lot of builtins-related boilerplate code. - [x] generate multiple method nodes for methods/constructors with varargs - [x] expanded processing to allow for @Builtin to be added to classes and and generate @BuiltinType classes - [x] generate code that wraps exceptions to panic via `wrapException` annotation element (see @Builtin.WrapException` Also rewrote @Builtin annotations to be more structured and introduced some nesting, such as @Builtin.Method or @Builtin.WrapException. This is part of incremental work and a follow up on https://github.com/enso-org/enso/pull/3444. # Important Notes Notice the number of boilerplate classes removed to see the impact. For now only applied to `Array` but should be applicable to other types.
2022-05-19 13:43:47 +03:00
- [Generate boilerplate classes related to error handling and varargs in
builtins from method signatures][3454]
Avoid needless concatenations of warning/error messages (#3465) While investigating [#182234656](https://www.pivotaltracker.com/n/projects/2539304/stories/182234656) I've noticed that `GatherDiagnostics` calls `distinctBy` and uses `message` string. However such string has to be composed and that takes time: ![image](https://user-images.githubusercontent.com/26887752/169638644-cf7dd826-1016-402b-842a-fc27a77a64e1.png) This PR eliminates the need for concatenation by associating each `Diagnostic` with an array of `keys` used to compute `equals` and `hashCode`.
2022-05-24 08:16:36 +03:00
- [Avoid needless concatenations of warning/error messages][3465]
Towards a full-blown builtins DSL (part 3) (#3471) Auto-generate all builtin methods for builtin `File` type from method signatures. Similarly, for `ManagedResource` and `Warning`. Additionally, support for specializations for overloaded and non-overloaded methods is added. Coverage can be tracked by the number of hard-coded builtin classes that are now deleted. ## Important notes Notice how `type File` now lacks `prim_file` field and we were able to get rid off all of those propagating method calls without writing a single builtin node class. Similarly `ManagedResource` and `Warning` are now builtins and `Prim_Warnings` stub is now gone.
2022-06-13 14:48:34 +03:00
- [Added a full-blown DSL for builtins][3471]
Enso Integration with Ideal Graph Visualizer (#3533) This PR adds sources for Enso language support in IGV (and NetBeans). The support is based on TextMate grammar shown in the editor and registration of the Enso language so IGV can find it. Then this PR adds new GitHub Actions workflow file to build the project using Maven.
2022-06-23 07:43:49 +03:00
- [Integration of Enso with Ideal Graph Visualizer][3533]
Short-circuiting || and && (#3492) Short-circuiting || and && is typically taken for granted by users of other PLs. This change makes it happen for Enso. Related to https://www.pivotaltracker.com/story/show/182261401
2022-06-02 19:58:38 +03:00
- [Lazy evaluation of RHS argument for || and &&][3492]
Minor compilation improvements (#3512) Drop `Core` implementation (replacement for IR) as it (sadly) looks increasingly unlikely this effort will be continued. Also, it heavily relies on implicits which increases some compilation time (~1sec from `clean`) Related to https://www.pivotaltracker.com/story/show/182359029
2022-06-07 17:48:50 +03:00
- [Drop Core implementation of IR][3512]
Substitute this with self (#3524) A semi-manual s/this/self appied to the whole standard library. Related to https://www.pivotaltracker.com/story/show/182328601 In the compiler promoted to use constants instead of hardcoded `this`/`self` whenever possible. # Important Notes The PR **does not** require explicit `self` parameter declaration for methods as this part of the design is still under consideration.
2022-06-21 13:53:52 +03:00
- [Replace `this` with `self`][3524]
introduce a micro stdlib for testing (#3531) This introduces a tiny alternative to our stdlib, that can be used for testing the interpreter. There are 2 main advantages of such a solution: 1. Performance: on my machine, `runtime-with-intstruments/test` drops from 146s to 65s, while `runtime/test` drops from 165s to 51s. >6 mins total becoming <2 mins total is awesome. This alone means I'll drink less coffee in these breaks and will be healthier. 2. Better separation of concepts – currently working on a feature that breaks _all_ enso code. The dependency of interpreter tests on the stdlib means I have no means of incremental testing – ALL of stdlib must compile. This is horrible, rendered my work impossible, and resulted in this PR.
2022-06-16 13:25:24 +03:00
- [Introduce a smaller version of the standard library, just for testing][3531]
Remove 'here' and make method name resolution case-sensitive (#3538) Modified UppercaseNames to now resolve methods without an explicit `here` to point to the current module. `here` was also often used instead of `self` which was allowed by the compiler. Therefore UppercaseNames pass is now GlobalNames and does some extra work - it translated method calls without an explicit target into proper applications. # Important Notes There was a long-standing bug in scopes usage when compiling standalone expressions. This resulted in AliasAnalysis generating incorrect graphs and manifested itself only in unit tests and when running `eval`, thus being a bit hard to locate. See `runExpression` for details. Additionally, method name resolution is now case-sensitive. Obsolete passes like UndefinedVariables and ModuleThisToHere were removed. All tests have been adapted.
2022-07-07 13:31:06 +03:00
- [Remove `here` and make method name resolution case-sensitive][3531]
Explicit self (#3569) This change modifies the current language by requiring explicit `self` parameter declaration for methods. Methods without `self` parameter in the first position should be treated as statics although that is not yet part of this PR. We add an implicit self to all methods This obviously required updating the whole stdlib and its components, tests etc but the change is pretty straightforward in the diff. Notice that this change **does not** change method dispatch, which was removed in the last changes. This was done on purpose to simplify the implementation for now. We will likely still remove all those implicit selfs to bring true statics. Minor caveat - since `main` doesn't actually need self, already removed that which simplified a lot of code.
2022-07-27 20:45:36 +03:00
- [Explicit `self`][3569]
Add Language Server benchmarking tool (#3578)
2022-07-22 17:12:52 +03:00
- [Added benchmarking tool for the language server][3578]
Support module imports using a qualified name (#3608) This change allows for importing modules using a qualified name and deals with any conflicts on the way. Given a module C defined at `A/B/C.enso` with ``` type C type C a ``` it is now possible to import it as ``` import project.A ... val x = A.B.C 10 ``` Given a module located at `A/B/C/D.enso`, we will generate intermediate, synthetic, modules that only import and export the successor module along the path. For example, the contents of a synthetic module B will look like ``` import <namespace>.<pkg-name>.A.B.C export <namespace>.<pkg-name>.A.B.C ``` If module B is defined already by the developer, the compiler will _inject_ the above statements to the IR. Also removed the last elements of some lowercase name resolution that managed to survive recent changes (`Meta.Enso_Project` would now be ambiguous with `enso_project` method). Finally, added a pass that detects shadowing of the synthetic module by the type defined along the path. We print a warning in such a situation. Related to https://www.pivotaltracker.com/n/projects/2539304 # Important Notes There was an additional request to fix the annoying problem with `from` imports that would always bring the module into the scope. The changes in stdlib demonstrate how it is now possible to avoid the workaround of ``` from X.Y.Z as Z_Module import A, B ``` (i.e. `as Z_Module` part is almost always unnecessary).
2022-07-29 17:19:07 +03:00
- [Support module imports using a qualified name][3608]
Use Rust Parser from Java instead of AST.scala (#3611)
2022-11-13 09:22:02 +03:00
- [Using parser written in Rust.][3611]
Enable caching in visualization functions (#3618) PR allows to attach metod pointers as a visualization expressions. This way it allows to attach a runtime instrument that enables caching of intermediate expressions. # Important Notes :information_source: API is backward compatible. To attach the visualization with caching support, the same `executionContext/attachVisualisation` method is used, but `VisualisationConfig` message should contain the message pointer. While `VisualisationConfiguration` message has changed, the language server accepts both new and old formats to keep visualisations working in IDE. #### Old format ```json { "executionContextId": "UUID", "visualisationModule": "local.Unnamed.Main", "expression": "x -> x.to_text" } ``` #### New format ```json { "executionContextId": "UUID", "expression": { "module": "local.Unnamed.Main", "definedOnType": "local.Unnamed.Main", "name": "encode" } } ```
2022-08-10 15:01:33 +03:00
- [Enable caching in visualisation functions][3618]
Update Scala to 2.13.8 (#3631) Update Scala compiler and libraries.
2022-08-08 22:32:55 +03:00
- [Update Scala compiler and libraries][3631]
Allow for importing methods (#3633) Importing individual methods didn't work as advertised because parser would allow them but later drop that information. This slipped by because we never had mixed atoms and methods in stdlib. # Important Notes Added some basic tests but we need to ensure that the new parser allows for this. @jdunkerley will be adding some changes to stdlib that will be testing this functionality as well.
2022-08-05 19:25:51 +03:00
- [Support importing module methods][3633]
Support Autosave for open buffers (#3637) This change adds Autosave action for open buffers. The action is scheduled after every edit request and is cancelled by every explicit save file request, if necessary. Successful autosave also notifies any active clients of the buffer. Related to https://www.pivotaltracker.com/story/show/182721656 # Important Notes WIP
2022-08-11 14:45:12 +03:00
- [Support Autosave for open buffers][3637]
Generate native image for engine-runner (#3638) This PR adds a possibility to generate native-image for engine-runner. Note that due to on-demand loading of stdlib, programs that make use of it are currently not yet supported (that will be resolved at a later point). The purpose of this PR is only to make sure that we can generate a bare minimum runner because due to lack TruffleBoundaries or misconfiguration in reflection config, this can get broken very easily. To generate a native image simply execute: ``` sbt> engine-runner-native/buildNativeImage ... (wait a few minutes) ``` The executable is called `runner` and can be tested via a simple test that is in the resources. To illustrate the benefits see the timings difference between the non-native and native one: ``` >time built-distribution/enso-engine-0.0.0-dev-linux-amd64/enso-0.0.0-dev/bin/enso --no-ir-caches --in-project test/Tests/ --run engine/runner-native/src/test/resources/Factorial.enso 6 720 real 0m4.503s user 0m9.248s sys 0m1.494s > time ./runner --run engine/runner-native/src/test/resources/Factorial.enso 6 720 real 0m0.176s user 0m0.042s sys 0m0.038s ``` # Important Notes Notice that due to a [bug in GraalVM](https://github.com/oracle/graal/issues/4200), which is already fixed in 22.x, and us still being on 21.x for the time being, I had to add a workaround to our sbt build to build a different fat jar for native image. To workaround it I had to exclude sqlite jar. Hence native image task is on `engine-runner-native` and not on `engine-runner`. Will need to add the above command to CI.
2022-09-22 17:45:10 +03:00
- [Generate native-image for engine-runner][3638]
Support pattern matching on constants (#3641) This change adds support for matching on constants by: 1) extending parser to allow literals in patterns 2) generate branch node for literals Related to https://www.pivotaltracker.com/story/show/182743559
2022-08-12 16:18:58 +03:00
- [Support pattern matching on constants][3641]
Builtin Date_Time, Time_Of_Day, Zone (#3658) * Builtin Date_Time, Time_Of_Day, Zone Improved polyglot support for Date_Time (formerly Time), Time_Of_Day and Zone. This follows the pattern introduced for Enso Date. Minor caveat - in tests for Date, had to bend a lot for JS Date to pass. This is because JS Date is not really only a Date, but also a Time and Timezone, previously we just didn't consider the latter. Also, JS Date does not deal well with setting timezones so the trick I used is to first call foreign function returning a polyglot JS Date, which is converted to ZonedDateTime and only then set the correct timezone. That way none of the existing tests had to be changes or special cased. Additionally, JS deals with milliseconds rather than nanoseconds so there is loss in precision, as noted in Time_Spec. * Add tests for Java's LocalTime * changelog * Make date formatters in table happy * PR review, add more tests for zone * More tests and fixed a bug in column reader Column reader didn't take into account timezone but that was a mistake since then it wouldn't map to Enso's Date_Time. Added tests that check it now. * remove redundant conversion * Update distribution/lib/Standard/Base/0.0.0-dev/src/Data/Time.enso Co-authored-by: Radosław Waśko <radoslaw.wasko@enso.org> * First round of addressing PR review * don't leak java exceptions in Zone * Move Date_Time to top-level module * PR review Co-authored-by: Radosław Waśko <radoslaw.wasko@enso.org> Co-authored-by: Jaroslav Tulach <jaroslav.tulach@enso.org>
2022-08-24 13:31:29 +03:00
- [Builtin Date_Time, Time_Of_Day and Zone types for better polyglot
support][3658]
Get rid of free-floating atoms. Everything has a type now! (#3671) This is a step towards the new language spec. The `type` keyword now means something. So we now have ``` type Maybe a Some (from_some : a) None ``` as a thing one may write. Also `Some` and `None` are not standalone types now – only `Maybe` is. This halfway to static methods – we still allow for things like `Number + Number` for backwards compatibility. It will disappear in the next PR. The concept of a type is now used for method dispatch – with great impact on interpreter code density. Some APIs in the STDLIB may require re-thinking. I take this is going to be up to the libraries team – some choices are not as good with a semantically different language. I've strived to update stdlib with minimal changes – to make sure it still works as it did. It is worth mentioning the conflicting constructor name convention I've used: if `Foo` only has one constructor, previously named `Foo`, we now have: ``` type Foo Foo_Data f1 f2 f3 ``` This is now necessary, because we still don't have proper statics. When they arrive, this can be changed (quite easily, with SED) to use them, and figure out the actual convention then. I have also reworked large parts of the builtins system, because it did not work at all with the new concepts. It also exposes the type variants in SuggestionBuilder, that was the original tiny PR this was based on. PS I'm so sorry for the size of this. No idea how this could have been smaller. It's a breaking language change after all.
2022-08-31 01:54:53 +03:00
- [Implement new specification of data types: `type` has a runtime
representation, every atom has a type][3671]
Print result of main (if not Nothing) (#3696) The goal of this request is to simplify hello world and other trivial Enso programs. No need to learn any standard library functions, enough to write: ``` main = "Hello World!" ``` and the result is going to be printed: ```bash enso$ ./built-distribution/enso-engine-0.0.0-dev-linux-amd64/enso-0.0.0-dev/bin/enso --run hello.enso 'Hello World!' ``` the result is only printed, if it is not `Nothing`. E.g. if the last statement is `IO.print ...` (which returns `Nothing`), then no value is printed at the end by the launcher.
2022-09-12 18:37:46 +03:00
- [main = "Hello World!" is valid Enso sample][3696]
Force recompilation if imported module has changed (#3703) IR cache never really took into account a situation when a binding from the imported module has changed. In other words, it would continue to happily use the serialized metadata without noticing that it changed. This change forces cache invalidation when any of the imported modules was invalidated (or rather not loaded from cache). # Important Notes Added simple test infrastructure that simulates file modifications that would trigger the initial cache invalidation. If they succeed, cache invalidation is propagated thus causing an error.
2022-09-15 16:41:58 +03:00
- [Invalidate module's IR cache if imported module changed][3703]
Don't rename imported Main module that only imports names (#3710) Turns that if you import a two-part import we had special code that would a) add Main submodule b) add an explicit rename. b) is problematic because sometimes we only want to import specific names. E.g., ``` from Bar.Foo import Bar, Baz ``` would be translated to ``` from Bar.Foo.Main as Foo import Bar, Baz ``` and it should only be translated to ``` from Bar.Foo.Main import Bar, Baz ``` This change detects this scenario and does not add renames in that case. Fixes [183276486](https://www.pivotaltracker.com/story/show/183276486).
2022-09-16 16:01:06 +03:00
- [Don't rename imported Main module that only imports names][3710]
Engine should send notification about node status (#3729) When nodes get invalidated in the cache, they have to be recomputed. Let the IDE know which of the nodes are pending by sending `Api.ExpressionUpdate.Payload.Pending` message. # Important Notes This PR introduces new `Api.ExpressionUpdate.Payload.Pending` message. This message is delivered before re-computation of nodes. Later `Api.ExpressionUpdate.Payload.Value` or other is sent to notify the IDE that a value for given node is available. Trivial implementation of of the `Api.ExpressionUpdate.Payload.Pending` message in the IDE is provided by this PR to (improperly) visualize pending node status - further improvements needed in follow up PRs.
2022-09-28 15:35:12 +03:00
- [Notify node status to the IDE][3729]
Static, but instance, but static (#3764) Adds the ability to write `Foo.method (Mk_Foo 123)` as a synonym of `(Mk_Foo 123).method` because Rust.
2022-10-10 22:28:33 +03:00
- [Make instance methods callable like statics][3764]
By-type pattern matching (#3742) This change brings by-type pattern matching to Enso. One can pattern match on Enso types as well as on polyglot types. For example, ``` case x of _ : Integer -> ... _ : Text -> ... _ -> ... ``` as well as Java's types ``` case y of _ : ArrayList -> ... _ : List -> ... _ : AbstractList -> ... _ -> .. ``` It is no longer possible to match a value with a corresponding type constructor. For example ``` case Date.now of Date -> ... ``` will no longer match and one should match on the type (`_ : Date`) instead. ``` case Date of Date -> ... ``` is fine though, as requested in the ticket. The change required further changes to `type_of` logic which wasn't dealing well with polyglot values. Implements https://www.pivotaltracker.com/story/show/183188846 # Important Notes ~I discovered late in the game that nested patterns involving type patterns, such as `Const (f : Foo) tail -> ...` are not possible due to the old parser logic. I would prefer to add it in a separate PR because this one is already getting quite large.~ This is now supported!
2022-10-04 12:23:58 +03:00
- [Distinguish static and instance methods][3740]
- [By-type pattern matching][3742]
Fix for perf degradation in method calls on polyglot arrays (#3781)
2022-10-10 19:35:38 +03:00
- [Fix performance of method calls on polyglot arrays][3781]
Don't add module's builtins to the scope of a builtin type (#3791) It appears that we were always adding builtin methods to the scope of the module and the builtin type that shared the same name. This resulted in some methods being accidentally available even though they shouldn't. This change treats differently builtins of types and modules and introduces auto-registration feature for builtins. By default all builtin methods are registered with a type, unless explicitly defined in the annotation property. Builtin methods that are auto-registered do not have to be explicitly defined and are registered with the underlying type. Registration correctly infers the right type, depending whether we deal with static or instance methods. Builtin methods that are not auto-registered have to be explicitly defined **always**. Modules' builtin methods are the prime example. # Important Notes Builtins now carry information whether they are static or not (inferred from the lack of `self` parameter). They also carry a `autoRegister` property to determine if a builtin method should be automatically registered with the type.
2022-11-16 13:23:52 +03:00
- [Improved support for static and non-static builtins][3791]
Missing foreign language generates proper Enso error. (#3798) Trying to invoke a foreign method with non-installed language (either not enabled in the Truffle `Context`, or not installed in the GraalVM distribution) results in `Polyglot_Error`, rather than crashing the entire engine.
2022-10-17 12:59:31 +03:00
- [Missing foreign language generates proper Enso error][3798]
Allow multiple exports of the same module (#3897) Previously, when exporting the same module multiple times only the first statement would count and the rest would be discarded by the compiler. This change allows for multiple exports of the same module e.g., ``` export project.F1 from project.F1 export foo ``` Multiple exports may however lead to conflicts when combined with hiding names. Added logic in `ImportResolver` to detect such scenarios. This fixes https://www.pivotaltracker.com/n/projects/2539304/stories/183092447 # Important Notes Added a bunch of scenarios to simulate pos and neg results.
2022-11-23 14:40:59 +03:00
- [Connecting IGV 4 Enso with Engine sources][3810]
Move logic calculating the index in Vector.at to a builtin method to make the performance of Vector to be on par with Array (#3811) The main culprit of a Vector slowdown (when compared to Array) was the normalization of the index when accessing the elements. Turns out that the Graal was very persistent on **not** inlining that particular fragment and that was degrading the results in benchmarks. Being unable to force it to do it (looks like a combination of thunk execution and another layer of indirection) we resorted to just moving the normalization to the builtin method. That makes Array and Vector perform roughly the same. Moved all handling of invalid index into the builtin as well, simplifying the Enso implementation. This also meant that `Vector.unsafe_at` is now obsolete. Additionally, added support for negative indices in Array, to behave in the same way as for Vector. # Important Notes Note that this workaround only addresses this particular perf issue. I'm pretty sure we will have more of such scenarios. Before the change `averageOverVector` benchmark averaged around `0.033 ms/op` now it does consistently `0.016 ms/op`, similarly to `averageOverArray`.
2022-10-20 15:50:44 +03:00
- [Made Vector performance to be on par with Array][3811]
State rework & IO Contexts (#3828) 1. Changes how we do monadic state – rather than a haskelly solution, we now have an implicit env with mutable data inside. It's better for the JVM. It also opens the possibility to have state ratained on exceptions (previously not possible) – both can now be implemented. 2. Introduces permission check system for IO actions.
2022-10-26 19:22:08 +03:00
- [Introduced IO Permission Contexts][3828]
Accept Array-like objects seamlessly in builtins (#3817) Most of the time, rather than defining the type of the parameter of the builtin, we want to accept every Array-like object i.e. Vector, Array, polyglot Array etc. Rather than writing all possible combinations, and likely causing bugs on the way anyway as we already saw, one should use `CoerceArrayNode` to convert to Java's `Object[]`. Added various test cases to illustrate the problem.
2022-10-25 15:44:48 +03:00
- [Accept Array-like object seamlessly in builtins][3817]
Initialize Builtins at Native Image build time (#3821) Moved loading of Builtin Types and Methods to a static initializer. That way the information is available at Native Image build time and one does not have to update a corresponding entry in `reflect-config` which would be a real pain when we start using it in anger. Fixes https://www.pivotaltracker.com/story/show/183374932
2022-10-25 21:28:10 +03:00
- [Initialize Builtins at Native Image build time][3821]
Split Atom suggestion entry to Type and Constructor (#3835) Changelog: - update: split `Atom` suggestion to `Type` and `Constructor` - update: gui API - update: JSONRPC doc
2022-11-02 12:53:40 +03:00
- [Split Atom suggestion entry to Type and Constructor][3835]
Allow conversion of EnsoBigInteger to double (#3865) Make sure any Enso number (including `EnsoBigInteger`) can be passed to Java via Truffle interop and used on the Java side.
2022-11-24 13:00:16 +03:00
- [Any number can be converted to double][3865]
Upgrade to GraalVM 22.3.0 (#3663) Upgrading to GraalVM 22.3.0. # Important Notes - Removed all deprecated `FrameSlot`, and replaced them with frame indexes - integers. - Add more information to `AliasAnalysis` so that it also gathers these indexes. - Add quick build mode option to `native-image` as default for non-release builds - `graaljs` and `native-image` should now be downloaded via `gu` automatically, as dependencies. - Remove `engine-runner-native` project - native image is now build straight from `engine-runner`. - We used to have `engine-runner-native` without `sqldf` in classpath as a workaround for an internal native image bug. - Fixed chrome inspector integration, such that it shows values of local variables both for current stack frame and caller stack frames. - There are still many issues with the debugging in general, for example, when there is a polyglot value among local variables, a `NullPointerException` is thrown and no values are displayed. - Removed some deprecated `native-image` options - Remove some deprecated Truffle API method calls.
2022-11-23 17:30:48 +03:00
- [Update to GraalVM 22.3.0][3663]
- [Connecting IGV 4 Enso with Engine sources][3810]
Allow multiple exports of the same module (#3897) Previously, when exporting the same module multiple times only the first statement would count and the rest would be discarded by the compiler. This change allows for multiple exports of the same module e.g., ``` export project.F1 from project.F1 export foo ``` Multiple exports may however lead to conflicts when combined with hiding names. Added logic in `ImportResolver` to detect such scenarios. This fixes https://www.pivotaltracker.com/n/projects/2539304/stories/183092447 # Important Notes Added a bunch of scenarios to simulate pos and neg results.
2022-11-23 14:40:59 +03:00
- [Add the `Self` keyword referring to current type][3844]
Project save backed by git (#3851) This change adds support for Version Controlled projects in language server. Version Control supports operations: - `init` - initialize VCS for a project - `save` - commit all changes to the project in VCS - `restore` - ability to restore project to some past `save` - `status` - show the status of the project from VCS' perspective - `list` - show a list of requested saves # Important Notes Behind the scenes, Enso's VCS uses git (or rather [jGit](https://www.eclipse.org/jgit/)) but nothing stops us from using a different implementation as long as it conforms to the establish API.
2022-11-14 20:32:39 +03:00
- [Support VCS for projects in Language Server][3851]
Allow multiple exports of the same module (#3897) Previously, when exporting the same module multiple times only the first statement would count and the rest would be discarded by the compiler. This change allows for multiple exports of the same module e.g., ``` export project.F1 from project.F1 export foo ``` Multiple exports may however lead to conflicts when combined with hiding names. Added logic in `ImportResolver` to detect such scenarios. This fixes https://www.pivotaltracker.com/n/projects/2539304/stories/183092447 # Important Notes Added a bunch of scenarios to simulate pos and neg results.
2022-11-23 14:40:59 +03:00
- [Support multiple exports of the same module][3897]
Import modules' extension methods only with unqualified import statements (#3906) # Important Notes Note that one cannot ``` import Standard.Table as Table_Module ``` because of the 2-component name restriction that gets desugared to `Standard.Table.Main` and we have to write ``` import Standard.Table.Main as Table_Module ``` in a few places. Once we move `Json.to_table` extension this can be improved.
2022-12-01 13:13:34 +03:00
- [Import modules' extension methods only with unqualified imports][3906]
Allow arbitrary expression evaluation in chromeinspector (#3941) Allow arbitrary expression evaluation in the chromeinspector console. Moreover, allow modifications of any variable in any stack frame. # Important Notes - Implement inline parsing in `EnsoLanguage.parse(InlineParsingRequest)`. - Debugging experience is affected by this [bug in Truffle](https://github.com/oracle/graal/issues/5513), which causes NPEs when a host object gets into chromeinspector. I tried to implement a workaround, but it does not work all the time. Nevertheless, it should not matter that much - if there is a NPE in the debugger, you can just ignore it, as it should be concealed in the debugger and should not be propagted outside. See comments in the `docs/debugger`.
2022-12-08 02:02:42 +03:00
- [Support expression evaluation in chromeinspector console][3941]
Don't export polyglot symbols (#3915) By default all polyglot symbols that have been imported were always exported. This means that importing a module that had some polyglot imports brought them into the scope automatically. This didn't follow our desired semantics. Fixes task 3 in https://www.pivotaltracker.com/story/show/183833055.
2022-11-28 22:11:31 +03:00
- [Don't export polyglot symbols][3915]
from/all import must not include module in name resolution (#3931) It appears that when were doing `from XYZ import all` the module `XYZ` was also being taken into account during name resolution. This was unfortunate and became problematic when one had a type with the same name defined in it. During pattern matching one could not simply do ``` from XYZ import all ... case ... of _ : XYZ -> ... ``` since the compiler would complain that we try to pattern match on a type but give it a module. The module is now excluded from the name resolution, when importing everything from the module. It appears that this "feature" was used in a number of our tests, so they had to be adapted. This fixes task 4 in https://www.pivotaltracker.com/story/show/183833055
2022-11-30 19:28:57 +03:00
- [From/all import must not include module in name resolution][3931]
Vector should preserve warnings (#3938) * Sequence literal (Vector) should preserve warnings When Vector was created via a sequence literal, we simply dropped any associated any warnings associated with it. This change propagates Warnings during the creation of the Vector. Ideally, it would be sufficient to propagate warnings from the individual elements to the underlying storage but doesn't go well with `Vector.fromArray`. * update changelog * Array-like structures preserver warnings Added a WarningsLibrary that exposes `hasWarnings` and `getWarnings` messages. That way we can have a single storage that defines how to extract warnings from an Array and the others just delegate to it. This simplifies logic added to sequence literals to handle warnings. * Ensure polyglot method calls are warning-free Since warnings are no longer automatically extracted from Array-like structures, we delay the operation until an actual polyglot method call is performed. Discovered a bug in `Warning.detach_selected_warnings` which was missing any usage or tests. * nits * Support multi-dimensional Vectors with warnings * Propagate warnings from case branches * nit * Propagate all vector warnings when reading element Previously, accessing an element of an Array-like structure would only return warnings of that element or of the structure itself. Now, accessing an element also returns warnings from all its elements as well.
2022-12-07 13:10:11 +03:00
- [Vector returns warnings of individual elements][3938]
Enso.getMetaObject, Type.isMetaInstance and Meta.is_a consolidation (#3949) Implements `getMetaObject` and related messages from Truffle interop for Enso values and types. Turns `Meta.is_a` into builtin and re-uses the same functionality. # Important Notes Adds `ValueGenerator` testing infrastructure to provide unified access to special Enso values and builtin types that can be reused by other tests, not just `MetaIsATest` and `MetaObjectTest`.
2022-12-22 11:00:06 +03:00
- [Enso.getMetaObject, Type.isMetaInstance and Meta.is_a consolidation][3949]
Add executionContext/interrupt API command (#3952) Implement the `executionContext/interrupt` API command that forcibly stops the program execution.
2022-12-08 03:04:46 +03:00
- [Add executionContext/interrupt API command][3952]
Convert Any.== to a builtin (#3956) `Any.==` is a builtin method. The semantics is the same as it used to be, except that we no longer assume `x == y` iff `Meta.is_same_object x y`, which used to be the case and caused failures in table tests. # Important Notes Measurements from `EqualsBenchmarks` shows that the performance of `Any.==` for recursive atoms increased by roughly 20%, and the performance for primitive types stays roughly the same.
2022-12-30 00:20:00 +03:00
- [Any.== is a builtin method][3956]
Simplify exception handling for polyglot exceptions (#3981) This removes the special handling of polyglot exceptions and allows matching on Java exceptions in the same way as for any other types. `Polyglot_Error`, `Panic.catch_java` and `Panic.catch_primitive` are gone The change mostly deals with the backslash of removing `Polyglot_Error` and two `Panic` methods. `Panic.catch` was implemented as a builtin instead of delegating to `Panic.catch_primitive` builtin that is now gone. This fixes https://www.pivotaltracker.com/story/show/182844611
2022-12-19 22:16:43 +03:00
- [Simplify exception handling for polyglot exceptions][3981]
Simplify compilation of nested patterns (#4005) `NestedPatternMatch` pass desugared complex patterns in a very inefficient way resulting in an exponential generation of the number of `case` IR (and Truffle) nodes. Every failed nested pattern would copy all the remaining patterns of the original case expression, in a desugared form. While the execution itself of such deeply nested `case` expression might not have many problems, the time spent in compilation phases certainly was a blocker. This change desugars deeply nested into individual cases with a fallthrough logic. However the fallthrough logic is implemented directly in Truffle nodes, rather than via IR. That way we can generate much simpler IR for nested patterns. Consider a simple case of ``` case x of Cons (Cons a b) Nil -> a + b Cons a Nil -> a _ -> 0 ``` Before the change, the compiler would generate rather large IR even for those two patterns: ``` case x of Cons w y -> case w of Cons a b -> case y of Nil -> a + b _ -> case x of Cons a z -> case z of Nil -> a _ -> case x of _ -> 0 _ -> 0 _ -> case x of Cons a z -> case z of Nil -> a _ -> case x of _ -> 0 _ -> 0 Cons a z -> case z of Nil -> a _ -> case x of _ -> 0 _ -> 0 ``` Now we generate simple patterns with fallthrough semantics and no catch-all branches: ``` case x of Cons w y -> case w of Cons a b -> case y of ## fallthrough on failed match ## Nil -> a + b ## fallthrough on failed match ## Cons a z -> case z of Nil -> a ## fallthrough on failed match ## _ -> 0 ``` # Important Notes If you wonder how much does it improve, then @radeusgd's example in https://www.pivotaltracker.com/story/show/183971366/comments/234688327 used to take at least 8 minutes to compile and run. Now it takes 5 seconds from cold start. Also, the example in the benchmark includes compilation time on purpose (that was the main culprit of the slowdown). For the old implementation I had to kill it after 15 minutes as it still wouldn't finish a single compilation. Now it runs 2 seconds or less. Bonus points: This PR will also fix problem reported in https://www.pivotaltracker.com/story/show/184071954 (duplicate errors for nested patterns)
2022-12-30 13:56:27 +03:00
- [Simplify compilation of nested patterns][4005]
IGV can jump to JMH sources & more (#4008) Improvements to behavior and visual appearance of IGV Enso integration.
2022-12-30 08:30:32 +03:00
- [IGV can jump to JMH sources & more][4008]
Basic VSCode support for Enso language and development (#4014) Basic VSCode support for Enso language and development # Important Notes See the [building instructions](https://github.com/enso-org/enso/pull/4014/files#diff-1f944b52bce988a17f27b2cdd35e0efe16a1df8b86ee6ced94c0a286033f1ab3R154).
2023-01-06 17:18:20 +03:00
- [Basic support of VSCode integration][4014]
Sync file system and language server after restore (#4020) VCS restore operation was correctly restoring the state of projects to the requested commit. Unfortunately, after the operation file system was becoming out-of-sync with language server's buffers (and IDE's content versions). A few important changes are introduced here that complicate the interaction between components: 1) `vcs restore` returns an actual diff between the current state and the requested commit 2) the response is forwarded to buffer registry first rather than to the client 3) the diff is used to identify appropriate collaborative editors and notify them about the need to reload buffers from file system 4) all clients of affected open buffers are notified of the change via `text/didChange` notification. If a file was removed and there were open buffers for it, clients will be notified via `file/event` and editor will be stopped 5) only then the client is notified about a successful restore operation This PR addresses one of the two problems reported in https://www.pivotaltracker.com/story/show/184097084. # Important Notes We need to make sure that IDE correctly responds to `text/didChange` notifications.
2023-01-05 17:00:00 +03:00
- [Sync language server with file system after VCS restore][4020]
Make ArrayOverBuffer behave like an Array/Array.sort no longer mutates the Array (#4022) Most of the problems with accessing `ArrayOverBuffer` have been resolved by using `CoerceArrayNode` (https://github.com/enso-org/enso/pull/3817). In `Array.sort` we still however specialized on Array which wasn't compatible with `ArrayOverBuffer`. Similarly sorting JS or Python arrays wouldn't work. Added a specialization to `Array.sort` to deal with that case. A generic specialization (with `hasArrayElements`) not only handles `ArrayOverBuffer` but also polyglot arrays coming from JS or Python. We could have an additional specialization for `ArrayOverBuffer` only (removed in the last commit) that returns `ArrayOverBuffer` rather than `Array` although that adds additional complexity which so far is unnecessary. Also fixed an example in `Array.enso` by providing a default argument.
2023-01-09 20:49:49 +03:00
- [`ArrayOverBuffer` behaves like an `Array` and `Array.sort` no longer sorts in
place][4022]
All Enso objects are hasheable (#3878) * Hash codes prototype * Remove Any.hash_code * Improve caching of hashcode in atoms * [WIP] Add Hash_Map type * Implement Any.hash_code builtin for primitives and vectors * Add some values to ValuesGenerator * Fix example docs on Time_Zone.new * [WIP] QuickFix for HashCodeTest before PR #3956 is merged * Fix hash code contract in HashCodeTest * Add times and dates values to HashCodeTest * Fix docs * Remove hashCodeForMetaInterop specialization * Introduce snapshoting of HashMapBuilder * Add unit tests for EnsoHashMap * Remove duplicate test in Map_Spec.enso * Hash_Map.to_vector caches result * Hash_Map_Spec is a copy of Map_Spec * Implement some methods in Hash_Map * Add equalsHashMaps specialization to EqualsAnyNode * get and insert operations are able to work with polyglot values * Implement rest of Hash_Map API * Add test that inserts elements with keys with same hash code * EnsoHashMap.toDisplayString use builder storage directly * Add separate specialization for host objects in EqualsAnyNode * Fix specialization for host objects in EqualsAnyNode * Add polyglot hash map tests * EconomicMap keeps reference to EqualsNode and HashCodeNode. Rather than passing these nodes to `get` and `insert` methods. * HashMapTest run in polyglot context * Fix containsKey index handling in snapshots * Remove snapshots field from EnsoHashMapBuilder * Prepare polyglot hash map handling. - Hash_Map builtin methods are separate nodes * Some bug fixes * Remove ForeignMapWrapper. We would have to wrap foreign maps in assignments for this to be efficient. * Improve performance of Hash_Map.get_builtin Also, if_nothing parameter is suspended * Remove to_flat_vector. Interop API requires nested vector (our previous to_vector implementation). Seems that I have misunderstood the docs the first time I read it. - to_vector does not sort the vector by keys by default * Fix polyglot hash maps method dispatch * Add tests that effectively test hash code implementation. Via hash map that behaves like a hash set. * Remove Hashcode_Spec * Add some polyglot tests * Add Text.== tests for NFD normalization * Fix NFD normalization bug in Text.java * Improve performance of EqualsAnyNode.equalsTexts specialization * Properly compute hash code for Atom and cache it * Fix Text specialization in HashCodeAnyNode * Add Hash_Map_Spec as part of all tests * Remove HashMapTest.java Providing all the infrastructure for all the needed Truffle nodes is no longer manageable. * Remove rest of identityHashCode message implementations * Replace old Map with Hash_Map * Add some docs * Add TruffleBoundaries * Formatting * Fix some tests to accept unsorted vector from Map.to_vector * Delete Map.first and Map.last methods * Add specialization for big integer hash * Introduce proper HashCodeTest and EqualsTest. - Use jUnit theories. - Call nodes directly * Fix some specializations for primitives in HashCodeAnyNode * Fix host object specialization * Remove Any.hash_code * Fix import in Map.enso * Update changelog * Reformat * Add truffle boundary to BigInteger.hashCode * Fix performance of HashCodeTest - initialize DataPoints just once * Fix MetaIsATest * Fix ValuesGenerator.textual - Java's char is not Text * Fix indent in Map_Spec.enso * Add maps to datapoints in HashCodeTest * Add specialization for maps in HashCodeAnyNode * Add multiLevelAtoms to ValuesGenerator * Provide a workaround for non-linear key inserts * Fix specializations for double and BigInteger * Cosmetics * Add truffle boundaries * Add allowInlining=true to some truffle boundaries. Increases performance a lot. * Increase the size of vectors, and warmup time for Vector.Distinct benchmark * Various small performance fixes. * Fix Geo_Spec tests to accept unsorted Map.to_vector * Implement Map.remove * FIx Visualization tests to accept unsorted Map.to_vector * Treat java.util.Properties as Map * Add truffle boundaries * Invoke polyglot methods on java.util.Properties * Ignore python tests if python lang is missing
2023-01-19 12:33:25 +03:00
- [Implement hashing functionality for all objects][3878]
Removing Unsafe.set_atom_field (#4023) Introducing `Meta.atom_with_hole` to create an `Atom` _with a hole_ that is then _safely_ filled in later.
2023-01-09 16:39:14 +03:00
- [Introducing Meta.atom_with_hole][4023]
Report failed name resolutions in type signatures (#4030) Compiler performed name resolution of literals in type signatures but would silently fail to report any problems. This meant that wrong names or forgotten imports would sneak in to stdlib. This change introduces 2 main changes: 1) failed name resolutions are appended in `TypeNames` pass 2) `GatherDiagnostics` pass also collects and reports failures from type signatures IR Updated stdlib so that it passes given the correct gatekeepers in place.
2023-01-09 13:35:36 +03:00
- [Report failures in name resolution in type signatures][4030]
Attach visualizations to sub-expressions (#4048) Add ability to attach visualizations to sub-expressions.
2023-01-16 13:19:19 +03:00
- [Attach visualizations to sub-expressions][4048]
Add Meta.get_annotation (#4049) - add: `GeneralAnnotation` IR node for `@name expression` annotations - update: compilation pipeline to process the annotation expressions - update: rewrite `OverloadsResolution` compiler pass so that it keeps the order of module definitions - add: `Meta.get_annotation` builtin function that returns the result of annotation expression - misc: improvements (private methods, lazy arguments, build.sbt cleanup)
2023-01-24 21:28:33 +03:00
- [Add Meta.get_annotation method][4049]
Resolve fully qualified names (#4056) Added a separate pass, `FullyQualifiedNames`, that partially resolves fully qualified names. The pass only resolves the library part of the name and replaces it with a reference to the `Main` module. There are 2 scenarios that could be potentially: 1) the code uses a fully qualified name to a component that has been parsed/compiled 2) the code uses a fully qualified name to a component that has **not** be imported For the former case, it is sufficient to just check `PackageRepository` for the presence of the library name. In the latter we have to ensure that the library has been already parsed and all its imports are resolved. That would require the reference to `Compiler` in the `FullyQualifiedNames` pass, which could then trigger a full compilation for missing library. Since it has some undesired consequences (tracking of dependencies becomes rather complex) we decided to exclude that scenario until it is really needed. # Important Notes With this change, one can use a fully qualified name directly. e.g. ``` import Standard.Base main = Standard.Base.IO.println "Hello world!" ```
2023-01-18 23:19:36 +03:00
- [Resolve Fully Qualified Names][4056]
Unboxed atoms (#3862) Introduces unboxed (and arity-specialized) storage schemes for Atoms. It results in improvements both in memory consumption and runtime. Memory wise: instead of using an array, we now use object fields. We also enable unboxing. This cuts a good few pointers in an unboxed object. E.g. a quadruple of integers is now 64 bytes (4x8 bytes for long fields + 16 bytes for layout and constructor pointers + 16 bytes for a class header). It used to be 168 bytes (4x24 bytes for boxed Longs + 16 bytes for array header + 32 bytes for array contents + 8 bytes for constructor ptr + 16 bytes for class header), so we're saving 104 bytes a piece. In the least impressive scenarios (all-boxed fields) we're saving 8 bytes per object (saving 16 bytes for array header, using 8 bytes for the new layout field). In the most-benchmarked case (list of longs), we save 32 bytes per cons-cell. Time wise: All list-summing benchmarks observe a ~2x speedup. List generation benchmarks get ~25x speedups, probably both due to less GC activity and better allocation characteristics (only allocating one object per Cons, rather than Cons + Object[] for fields). The "map-reverse" family gets a neat 10x speedup (part of the work is reading, which is 2x faster, the other is allocating, which is now 25x faster, we end up with 10x when combined).
2023-01-24 16:03:06 +03:00
- [Optimize Atom storage layouts][3862]
Create static wrappers for builtin types (#4077) https://github.com/enso-org/enso/pull/3764 introduced static wrappers for instance methods. Except it had a limitation to only be allowed for types with at least a single constructor. That excluded builtin types as well which, by default, don't have them. This limitation is problematic for Array/Vector consolidation and makes builtin types somehow second-citizens. This change lifts the limitation for builtin types only. Note that we do want to share the implementation of the generated builtin methods. At the same time due to the additional argument we have to adjust the starting index of the arguments. This change avoids messing with the existing dispatch logic, to avoid unnecessary complexity. As a result it is now possible to call builtin types' instance methods, statically: ``` arr = Array.new_1 42 Array.length arr ``` That would previously lead to missing method exception in runtime. # Important Notes The only exception is `Nothing`. Primarily because it requires `Nothing` to have a proper eigentype (`Nothing.type`) which would messed up a lot of existing logic for no obvious benefit (no more calling of `foo=Nothing` in parameters being one example).
2023-01-30 22:54:51 +03:00
- [Make instance methods callable like statics for builtin types][4077]
Custom type conversion to double from large long (#4099) When a large long would be passed to a host call expecting a double, it would crash with a ``` Cannot convert '<some long>'(language: Java, type: java.lang.Long) to Java type 'double': Invalid or lossy primitive coercion ``` That is unlikely to be expected by users. It also came up in the Statistics examples during Sum. One could workaround it by forcing the conversion manually with `.to_decimal` but it is not a permanent solution. Instead this change adds a custom type mapping from Long to Double that will do it behind the scenes with no user interaction. The mapping kicks in only for really large longs. # Important Notes Note that the _safe_ range is hardcoded in Truffle and it is not accessible in enso packages. Therefore a simple c&p for that max safe long value was necessary.
2023-01-31 18:13:00 +03:00
- [Convert large longs to doubles, safely, for host calls][4099]
Report only unique warnings (#6372) This change makes sure that reported warnings are unique, based on the value of internal clock tick and ignoring differences in reassignments. Before: ![Screenshot from 2023-04-20 15-42-55](https://user-images.githubusercontent.com/292128/233415710-925c1045-37c7-49f5-9bc3-bfbfd30270a3.png) After: ![Screenshot from 2023-04-20 15-27-27](https://user-images.githubusercontent.com/292128/233415807-8cb67bc2-ac37-4db7-924e-ae7619074b5b.png) On the positive side, no further changes, like in LS, have to be done. Closes #6257.
2023-04-28 10:16:00 +03:00
- [Consistent ordering with comparators][4067]
Write the log in XML format suitable for VisualVM 'UI Actions' (#4110) Start `project-manager` with following options to provide first 20s of the startup sequence: ``` $ project-manager --profiling-events-log-path=start.log --profiling-path=start.npss --profiling-time=20 ``` once the `start.log` and `start.npss` files are generated (next to each other), open them in GraalVM's VisualVM: ``` $ graalvm/bin/jvisualvm --openfile start.npss ``` analyze.
2023-02-05 09:36:16 +03:00
- [Profile engine startup][4110]
Report type of expressions returning polyglot values (#4111) Expressions returning polyglot values were not reporting the type of the result because we have to do additional magic that infers the correct Enso type. Since this is exactly what `TypeOfNode` does, I re-used the logic. Straightforward solution failed in tests because of assertions: ``` [enso] WARNING: Execution of function main failed (Invalid library usage. Cached library must be adopted by a RootNode before it is executed.). java.lang.AssertionError: Invalid library usage. Cached library must be adopted by a RootNode before it is executed. ``` That is why this PR replaces `ExecutionEventListener` with `ExecutionEventNodeFactory`. # Important Notes Usage of `TypeOfNode` for programs that **do not** import stdlib means that we report types that do not involve stdlib e.g. `Standard.Builtins.Main.Integer` instead of `Standard.Base.Data.Numbers.Integer`. While surprising, this is correct and I would say desirable. While reviewing the code, notice the difference in expectations in our runtime tests.
2023-02-09 04:06:27 +03:00
- [Report type of polyglot values][4111]
Recover from serialization failures (#5591) An exception encountered during serialization prevents engine from continuing because it enters an infinite loop(!). # Important Notes The aim of this PR is to make it possible for engine to recover from the serialization failures. Any failure would mean that we enter an infinite loop in deserialization which is in turn waiting for the serialization to finish (which will never happen). In this particular case FQNs are [referencing concrete modules](https://github.com/enso-org/enso/issues/5037). A separate PR will address that.
2023-02-09 11:22:28 +03:00
- [Engine can now recover from serialization failures][5591]
sbt runEngineDistribution ...args... to build and execute the engine (#5609) Automating the assembly of the engine and its execution into a single task. If you are modifying standard libraries, engine sources or Enso tests, you can launch `sbt` and then just: ``` sbt:enso> runEngineDistribution --run test/Tests/src/Data/Maybe_Spec.enso [info] Engine package created at built-distribution/enso-engine-0.0.0-dev-linux-amd64/enso-0.0.0-dev [info] Executing built-distribution/enso-engine-...-dev/bin/enso --run test/Tests/src/Data/Maybe_Spec.enso Maybe: [5/5, 30ms] - should have a None variant [14ms] - should have a Some variant [5ms] - should provide the `maybe` function [4ms] - should provide `is_some` [2ms] - should provide `is_none` [3ms] 5 tests succeeded. 0 tests failed.unEngineDistribution 4s 0 tests skipped. ``` the [runEngineDistribution](https://github.com/enso-org/enso/blob/3a581f29eec74d54f53271bebbc0d3503c6615e7/docs/CONTRIBUTING.md#running-enso) `sbt` input task makes sure all your sources are properly compiled and only then executes your enso source. Everything ready at a single press of Enter. # Important Notes To debug in chrome dev tools, just add `--inspect`: ``` sbt:enso> runEngineDistribution --inspect --run test/Tests/src/Data/Maybe_Spec.enso E.g. in Chrome open: devtools://devtools/bundled/js_app.html?ws=127.0.0.1:9229/7JsgjXlntK8 ``` everything gets build and one can just attach the Enso debugger.
2023-02-17 00:37:12 +03:00
- [Use sbt runEngineDistribution][5609]
Update GraalVM to 22.3.1 (#5602) Updates the engine to GraalVM 22.3.1 version, which contains fixes for: - Chrome inspector issues - https://github.com/enso-org/enso/pull/3941/commits/38eb3b5932d91fe858c9ba96b9a0543118bd2364 # Important Notes - Update to GraalVM 22.3.1 - Remove host object wrapping workaround
2023-02-14 18:51:17 +03:00
- [Update to GraalVM 22.3.1][5602]
Optimize import/export resolution (#5700) This change adds serialization and deserialization of library bindings. In order to be functional, one needs to first generate IR and serialize bindings using `--compiled <path-to-library>` command. The bindings will be stored under the library with `.bindings` suffix. Bindings are being generated during `buildEngineDistribution` task, thus not requiring any extra steps. When resolving import/exports the compiler will first try to load module's bindings from cache. If successful, it will not schedule its imports/exports for immediate compilation, as we always did, but use the bindings info to infer the dependent modules. The current change does not make any optimizations when it comes to compiling the modules, yet. It only delays the actual compilation/loading IR from cache so that it can be done in bulk. Further optimizations will come from this opportunity such as parallel loading of caches or lazily inferring only the necessary modules. Part of https://github.com/enso-org/enso/issues/5568 work.
2023-03-01 11:53:29 +03:00
- [Cache library bindings to optimize import/export resolution][5700]
Comparators support partial ordering (#5778)
2023-03-07 07:16:38 +03:00
- [Comparators support partial ordering][5778]
Merge ordered and unordered comparators (#5845) Merge _ordered_ and _unordered_ comparators into a single one. # Important Notes Comparator is now required to have only `compare` method: ``` type Comparator comapre : T -> T -> (Ordering|Nothing) hash : T -> Integer ```
2023-03-11 08:43:22 +03:00
- [Merge ordered and unordered comparators][5845]
Downgrade hashing to SHA-1 and other optimizations (#5791) This change downgrades hashing algorithm used in caching IR and library bindings to SHA-1. It is sufficient and significantly faster for the purpose of simple checksum we use it for. Additionally, don't calculate the digest for serialized bytes - if we get the expected object type then we are confident about the integrity. Don't initialize Jackson's ObjectMapper for every metadata serialization/de-serialization. Initialization is very costly. Avoid unnecessary conversions between Scala and Java. Those back-and-forth `asScala` and `asJava` are pretty expensive. Finally fix an SBT warning when generating library cache. Closes https://github.com/enso-org/enso/issues/5763 # Important Notes The change cuts roughly 0.8-1s from the overall startup. This change will certainly lead to invalidation of existing caches. It is advised to simply start with a clean slate.
2023-03-09 10:36:59 +03:00
- [Use SHA-1 for calculating hashes of modules' IR and bindings][5791]
Don't log installed engines and runtimes in prod (#5900) The `logAvailableComponentsForDebugging` will check and install all necessary components of GraalVM for every mentioned version. While not harmful, it adds up to startup time. Additionally added an option in language server startup to skip installation of GraalVM components. The latter is already performed by project-manager when opening the project and it is unnecessary to do it twice. Due to LS' architecture this configuration has to be passed around via multiple configs. Finally, skipped the attempt to install Python component on Windows - this is not supported by GraalVM atm. Closes #5749. # Important Notes The impact of this problem could be really felt the more versions of Enso and GraalVM one had since it would go through all of them.
2023-03-16 13:36:55 +03:00
- [Don't install Python component on Windows][5900]
Detect conflicts between exported types and FQNs (#5986) Exporting types named the same as the module where they are defined in `Main` modules of library components may lead to accidental name conflicts. This became apparent when trying to access `Problem_Behavior` module via a fully qualified name and the compiler rejected it. This is due to the fact that `Main` module exported `Error` type defined in `Standard.Base.Error` module, thus making it impossible to access any other submodules of `Standard.Base.Error` via a fully qualified name. This change adds a warning to FullyQualifiedNames pass that detects any such future problems. While only `Error` module was affected, it was widely used in the stdlib, hence the number of changes. Closes #5902. # Important Notes I left out the potential conflict in micro-distribution, thus ensuring we actually detect and report the warning.
2023-03-22 00:09:41 +03:00
- [Detect potential name conflicts between exported types and FQNs][5966]
Ensure new and wrapper nodes inherit UUID (#6067) Instrumentation of calls involving warning values never really worked because: 1) newly created nodes didn't set the UUID of their children 2) the instrumentable wrappers always had an empty (i.e. null) UUID and they never referred `get`/`setId` calls to their delegates On the surface, everything worked fine. Except when one actually relied on the instrumentation of values with warnings for proper setup. Then no instrumentation (replacement of nodes) was performed due to empty UUID (as required by `hasTag` of `FunctionCallInstrumentationNode`). Closes #6045. Discovered in #5893.
2023-03-27 20:49:20 +03:00
- [Ensure calls involving warnings remain instrumented][6067]
Suspended atom fields are evaluated only once (#6151) Implements #6134. # Important Notes One can define lazy atom fields as: ```haskell type Lazy Value ~x ~y ``` the evaluation of the `x` and `y` fields is then delayed until they are needed. The evaluation happens once. Then the computed value is kept in the atom for further use.
2023-04-06 02:46:08 +03:00
- [One can define lazy atom fields][6151]
Replace IOContexts with execution env and contexts (#6171) As per design, IOContexts controlled via type signatures are going away. They are replaced by explicit `Context.if_enabled` runtime checks that will be added to particular method implementations. `production`/`development` `IOPermissions` are replaced with `live` and `design` execution enviornment. Currently, the `live` env has a hardcoded list of allowed contexts i.e. `Input` and `Output`. # Important Notes As per design PR-55. Closes #6129. Closes #6131.
2023-04-06 18:47:40 +03:00
- [Replace IOContexts with Execution Environment and generic Context][6171]
sort handles incomparable values (#5998) * Update type ascriptions in some operators in Any * Add @GenerateUncached to AnyToTextNode. Will be used in another node with @GenerateUncached. * Add tests for "sort handles incomparable types" * Vector.sort handles incomparable types * Implement sort handling for different comparators * Comparison operators in Any do not throw Type_Error * Fix some issues in Ordering_Spec * Remove the remaining comparison operator overrides for numbers. * Consolidate all sorting functionality into a single builtin node. * Fix warnings attachment in sort * PrimitiveValuesComparator handles other types than primitives * Fix byFunc calling * on function can be called from the builtin * Fix build of native image * Update changelog * Add VectorSortTest * Builtin method should not throw DataflowError. If yes, the message is discarded (a bug?) * TypeOfNode may not return only Type * UnresolvedSymbol is not supported as `on` argument to Vector.sort_builtin * Fix docs * Fix bigint spec in LessThanNode * Small fixes * Small fixes * Nothings and Nans are sorted at the end of default comparator group. But not at the whole end of the resulting vector. * Fix checking of `by` parameter - now accepts functions with default arguments. * Fix changelog formatting * Fix imports in DebuggingEnsoTest * Remove Array.sort_builtin * Add comparison operators to micro-distribution * Remove Array.sort_builtin * Replace Incomparable_Values by Type_Error in some tests * Add on_incomparable argument to Vector.sort_builtin * Fix after merge - Array.sort delegates to Vector.sort * Add more tests for problem_behavior on Vector.sort * SortVectorNode throws only Incomparable_Values. * Delete Collections helper class * Add test for expected failure for custom incomparable values * Cosmetics. * Fix test expecting different comparators warning * isNothing is checked via interop * Remove TruffleLogger from SortVectorNode * Small review refactorings * Revert "Remove the remaining comparison operator overrides for numbers." This reverts commit 0df66b10806036594cf51b13df6062ab32680689. * Improve bench_download.py tool's `--compare` functionality. - Output table is sorted by benchmark labels. - Do not fail when there are different benchmark labels in both runs. * Wrap potential interop values with `HostValueToEnsoNode` * Use alter function in Vector_Spec * Update docs * Invalid comparison throws Incomparable_Values rather than Type_Error * Number comparison builtin methods return Nothing in case of incomparables
2023-04-16 17:40:12 +03:00
- [Vector.sort handles incomparable types][5998]
Removing need for asynchronous thread to execute ResourceManager finalizers (#6335) While Enso runs single-threaded, its `ResourceManager` required additional asynchronous thread to execute its _"finalizers"_. What has been necessary back then is no longer needed since _GraalVM 21.1_. GraalVM now provides support for submitting `ThreadLocalAction` that gets then picked and executed via `TruffleSafepoint` locations. This PR uses such mechanism to _"inject"_ finalizer execution into already running Enso evaluation thread. Requiring more than one thread has complicated Enso's co-existence with other Truffle language. For example Graal.js is strictly singlethreaded and used to refuse (simple) co-existence with Enso. By allowing Enso to perform all its actions in a single thread, the synergy with Graal.js becomes better.
2023-04-20 14:33:45 +03:00
- [Removing need for asynchronous thread to execute ResourceManager
finalizers][6335]
Report only unique warnings (#6372) This change makes sure that reported warnings are unique, based on the value of internal clock tick and ignoring differences in reassignments. Before: ![Screenshot from 2023-04-20 15-42-55](https://user-images.githubusercontent.com/292128/233415710-925c1045-37c7-49f5-9bc3-bfbfd30270a3.png) After: ![Screenshot from 2023-04-20 15-27-27](https://user-images.githubusercontent.com/292128/233415807-8cb67bc2-ac37-4db7-924e-ae7619074b5b.png) On the positive side, no further changes, like in LS, have to be done. Closes #6257.
2023-04-28 10:16:00 +03:00
- [Warning.get_all returns only unique warnings][6372]
Reimplement `enso_project` as a proper builtin (#6352) Remove the magical code generation of `enso_project` method from codegen phase and reimplement it as a proper builtin method. The old behavior of `enso_project` was special, and violated the language semantics (regarding the `self` argument): - It was implicitly declared in every module, so it could be called without a self argument. - It can be called with explicit module as self argument, e.g. `Base.enso_project`, or `Visualizations.enso_project`. Let's avoid implicit methods on modules and let's be explicit. Let's reimplement the `enso_project` as a builtin method. To comply with the language semantics, we will have to change the signature a bit: - `enso_project` is a static method in the `Standard.Base.Meta.Enso_Project` module. - It takes an optional `project` argument (instead of taking it as an explicit self argument). Having the `enso_project` defined as a (shadowed) builtin method, we will automatically have suggestions created for it. # Important Notes - Truffle nodes are no longer generated in codegen phase for the `enso_project` method. It is a standard builtin now. - The minimal import to use `enso_project` is now `from Standard.Base.Meta.Enso_Project import enso_project`. - Tested implicitly by `org.enso.compiler.ExecCompilerTest#testInvalidEnsoProjectRef`.
2023-05-02 19:40:58 +03:00
- [Reimplement `enso_project` as a proper builtin][6352]
Limit the number of reported warnings (#6577) Artifically limiting the number of reported warnings to 100. Also added benchmarks with random Ints to investigate perf issues when dealing with warnings (future task). Ideally we would have a custom set-like collection that allows us internally to specify a maximal number of elements. But `EnsoHashMap` (and potentially `EnsoSet`) are still WIP when it comes to being PE-friendly. The change also allows for checking if the limit for the number of reported warnings has been reached. It will visualize by adding an additional "Warnings limit reached." to the visualization. The limit is configurable via `--warnings-limit` parameter to `run`. Closes #6283.
2023-05-10 14:48:31 +03:00
- [Limit number of reported warnings per value][6577]
Only send suggestions updates when type changes (#6755) The change adds an additional field to `ExpressionUpdates` messages sent by `ProgramExecutionSupport` to indicate if the type of value (or its method pointer) has changed and therefore would potentially require a suggestions' update. Prior to #3729 that check was done during the instrumentation. However we still want to continue to support "pending expression" functionality therefore `SuggestionsHandler` will use the additional information to filter only the required expression updates. Most of the changes are related to adapting our tests to the new field. Closes #6706. # Important Notes The associated project now loads and navigates smoothly. Also attaching a screenshot from the project that illustrates that pending functionality continues to work: [Kazam_screencast_00006.webm](https://github.com/enso-org/enso/assets/292128/35918841-f84f-4e1c-b1b0-40e45d97e111)
2023-05-18 19:44:38 +03:00
- [Suggestions are updated only when the type of the expression changes][6755]
Add project creation time to project metadata (#6780) close #6686 Changelog: - add: `created` field to the project metadata response - update: project manager tests
2023-05-22 16:40:10 +03:00
- [Add project creation time to project metadata][6780]
Update GraalVM to 22.3.1 JDK17 (#6750) Upgrade GraalVM to 22.3.2 based on JDK17. --------- Co-authored-by: somebody1234 <ehern.lee@gmail.com>
2023-05-24 11:39:08 +03:00
- [Upgrade GraalVM to 22.3.1 JDK17][6750]
Runtime check of ascribed types (#6790)
2023-05-30 12:07:26 +03:00
- [Ascribed types are checked during runtime][6790]
Add compiler pass that discovers ambiguous imports (#6868) Add a new compiler pass that analyses duplicated and ambiguous symbols from imports
2023-06-14 13:18:57 +03:00
- [Add compiler pass that discovers ambiguous and duplicated symbols][6868]
Improve compiler's diagnostic messages (#6931) Improve and colorize compiler's messages. Heavily inspired by `gcc`.
2023-06-08 18:43:18 +03:00
- [Improve and colorize compiler's diagnostic messages][6931]
Eliminate race condition for edit/close/open cmds (#6998) There was an inherent race condition between edit, close & open commands which could not be prevented solely using locks. `EditFileCmd` triggered `EnsureCompiledJob` which was applying edits collected over time. At the same `CloseFileCmd` and `OpenFileCmd` were executed asynchronously and required locks on compilation unit and file lock. Additionally, open file was resetting the module's runtime source irrespective of any edits that could already have been applied with the asynchronous execution in `EnsureCompiledJob`. This was visible especially during early manipulation of the project when open/close was performed due to a bug in IDE (#6843). Now commands can be run either synchronously or asynchronously. Only that way can we ensure that `close` & `open` commands finish by the time any editions are being applied to module's sources. Closes #6841. # Important Notes In the given video, `"foo"` would be greyed out because it would never be part of the module's (runtime) sources. Therefore no IR would be generated for it or instrumentation, meaning it would be present in `expressionUpdates` information necessary for IDE. [Kazam_screencast_00014.webm](https://github.com/enso-org/enso/assets/292128/226a17b8-729a-415a-803f-003a9695b2f1)
2023-06-09 15:12:46 +03:00
- [Execute some runtime commands synchronously to avoid race conditions][6998]
Scala 2.13.11 and libraries update (#7010) Update Scala and libraries.
2023-06-14 16:15:57 +03:00
- [Scala 2.13.11 update][7010]
Improvements that significantly reduce the chances of request timeouts (#7042) Request Timeouts started plaguing IDE due to numerous `executionContext/***Visualization` requests. While caused by a bug they revealed a bigger problem in the Language Server when serving large amounts of requests: 1) Long and short lived jobs are fighting for various locks. Lock contention leads to some jobs waiting for a longer than desired leading to unexpected request timeouts. Increasing timeout value is just delaying the problem. 2) Requests coming from IDE are served almost instantly and handled by various commands. Commands can issue further jobs that serve request. We apparently have and always had a single-thread thread pool for serving such jobs, leading to immediate thread starvation. Both reasons increase the chances of Request Timeouts when dealing with a large number of requests. For 2) I noticed that while we used to set the `enso-runtime-server.jobParallelism` option descriptor key to some machine-dependent value (most likely > 1), the value set would **only** be available for instrumentation. `JobExecutionEngine` where it is actually used would always get the default, i.e. a single-threaded ThreadPool. This means that this option descriptor was simply misused since its introduction. Moved that option to runtime options so that it can be set and retrieved during normal operation. Adding parallelism intensified problem 1), because now we could execute multiple jobs and they would compete for resources. It also revealed a scenario for a yet another deadlock scenario, due to invalid order of lock acquisition. See `ExecuteJob` vs `UpsertVisualisationJob` order for details. Still, a number of requests would continue to randomly timeout due to lock contention. It became apparent that `Attach/Modify/Detach-VisualisationCmd` should not wait until a triggered `UpsertVisualisationJob` sends a response to the client; long and short lived jobs will always compete for resources and we cannot guarantee that they will not timeout that way. That is why the response is sent immediately from the command handler and not from the job executed after it. This brings another problematic scenario: 1. `AttachVisualisationCmd` is executed, response sent to the client, `UpsertVisualisationJob` scheduled. 2. In the meantime `ModifyVisualisationCmd` comes and fails; command cannot find the visualization that will only be added by `UpsertVisualisationJob`, which might have not yet been scheduled to run. Remedied that by checking visualisation-related jobs that are still in progress. It also allowed for cancelling jobs which results wouldn't be used anyway (`ModifyVisualisationCmd` sends its own `UpsertVisualisationJob`). This is not a theoretical scenario, it happened frequently on IDE startup. This change does not fully solve the rather problematic setup of numerous locks, which are requested by short and long lived jobs. A better design should still be investigated. But it significantly reduces the chances of Request Timeouts which IDE had to deal with. With this change I haven't been able to experience Request Timeouts for relatively modest projects anymore. I added the possibility of logging wait times for locks to better investigate further problems. Closes #7005
2023-06-16 20:57:16 +03:00
- [Improve parallel execution of commands and jobs in Language Server][7042]
Implement conversions (#180312665) (#3227) * Implement conversions start wip branch for conversion methods for collaborating with marcin add conversions to MethodDispatchLibrary (wip) start MethodDispatchLibrary implementations conversions for atoms and functions Implement a bunch of missing conversion lookups final bug fixes for merged methoddispatchlibrary implementations UnresolvedConversion.resolveFor progress on invokeConversion start extracting constructors (still not working) fix a bug add some initial conversion tests fix a bug in qualified name resolution, test conversions accross modules implement error reporting, discover a ton of ignored errors... start fixing errors that we exposed in the standard library fix remaining standard lib type errors not caused by the inability to parse type signatures for operators TODO: fix type signatures for operators. all of them are broken fix type signature parsing for operators test cases for meta & polyglot play nice with polyglot start pretending unresolved conversions are unresolved symbols treat UnresolvedConversons as UnresolvedSymbols in enso user land * update RELEASES.md * disable test error about from conversions being tail calls. (pivotal issue #181113110) * add changelog entry * fix OverloadsResolutionTest * fix MethodDefinitionsTest * fix DataflowAnalysisTest * the field name for a from conversion must be 'that'. Fix remaining tests that aren't ExpressionUpdates vs. ExecutionUpdate behavioral changes * fix ModuleThisToHereTest * feat: suppress compilation errors from Builtins * Revert "feat: suppress compilation errors from Builtins" This reverts commit 63d069bd4f059baad76b7b421c4a1330ea5ffea5. * fix tests * fix: formatting Co-authored-by: Dmitry Bushev <bushevdv@gmail.com> Co-authored-by: Marcin Kostrzewa <marckostrzewa@gmail.com>
2022-02-06 12:02:09 +03:00
[3227]: https://github.com/enso-org/enso/pull/3227
Decorate values with arbitrary warnings (#3248)
2022-03-09 18:40:02 +03:00
[3248]: https://github.com/enso-org/enso/pull/3248
Upgrade Truffle and Graal to Version 21.3.0 (#3258)
2022-02-11 19:05:13 +03:00
[3258]: https://github.com/enso-org/enso/pull/3258
Initialize AtomConstructor's fields via local vars (#3330) The mechanism follows a similar approach to what is being in functions with default arguments. Additionally since InstantiateAtomNode wasn't a subtype of EnsoRootNode it couldn't be used in the application, which was the primary reason for issue #181449213. Alternatively InstantiateAtomNode could have been enhanced to extend EnsoRootNode rather than RootNode to carry scope info but the former seemed simpler. See test cases for previously crashing and invalid cases.
2022-03-21 12:15:14 +03:00
[3330]: https://github.com/enso-org/enso/pull/3330
Always call defaulted atom arguments (#3358) Solves the issue of defaulted args not being called in atoms. Doesn't solve the more general function issue.
2022-04-08 11:21:59 +03:00
[3358]: https://github.com/enso-org/enso/pull/3358
Implement Documentation Sections API (#3360)
2022-03-25 10:49:37 +03:00
[3360]: https://github.com/enso-org/enso/pull/3360
Fix resource management in ModuleCache (#3367) PR fixes an issue when compiler crashes while trying to load an incompatible `IR` cache.
2022-03-29 16:47:03 +03:00
[3367]: https://github.com/enso-org/enso/pull/3367
Improved polyglot Date support (#3559) Significantly improves the polyglot Date support (as introduced by #3374). It enhances the `Date_Spec` to run it in four flavors: - with Enso Date (as of now) - with JavaScript Date - with JavaScript Date wrapped in (JavaScript) array - with Java LocalDate allocated directly The code is then improved by necessary modifications to make the `Date_Spec` pass. # Important Notes James has requested in [#181755990](https://www.pivotaltracker.com/n/projects/2539304/stories/181755990) - e.g. _Review and improve InMemory Table support for Dates, Times, DateTimes, BigIntegers_ the following program to work: ``` foreign js dateArr = """ return [1, new Date(), 7] main = IO.println <| (dateArr.at 1).week_of_year ``` the program works with here in provided changes and prints `27` as of today. @jdunkerley has provided tests for proper behavior of date in `Table` and `Column`. Those tests are working as of [f16d07e](https://github.com/enso-org/enso/pull/3559/commits/f16d07e640c12721eb329a797a19c7b46bbf3fbc). One just needs to accept `List<Value>` and then query `Value` for `isDate()` when needed. Last round of changes is related to **exception handling**. https://github.com/enso-org/enso/pull/3559/commits/8b686b12bdc1113e07ff37bc780df960aae34039 makes sure `makePolyglotError` accepts only polyglot values. Then it wraps plain Java exceptions into `WrapPlainException` with `has_type` method - https://github.com/enso-org/enso/pull/3559/commits/60da5e70ed58db55e00bf82f57f47063a6d1e587 - the remaining changes in the PR are only trying to get all tests working in the new setup. The support for `Time` isn't part of this PR yet.
2022-07-21 09:32:40 +03:00
[3559]: https://github.com/enso-org/enso/pull/3559
Avoid whole source reparsing when the IDE performs a simple edit (#3508) Co-authored-by: Dmitry Bushev <bushevdv@gmail.com> Co-authored-by: Hubert Plociniczak <hubert.plociniczak@gmail.com>
2022-06-16 17:02:57 +03:00
[3508]: https://github.com/enso-org/enso/pull/3508
Load component group modules (#3412)
2022-04-25 18:09:09 +03:00
[3412]: https://github.com/enso-org/enso/pull/3412
Automatically force all-defaulted functions (#3414) This changes the interpreter to treat functions with all-defaulted args as thunks. Seems to have no performance impact in compiled code.
2022-04-27 20:57:00 +03:00
[3414]: https://github.com/enso-org/enso/pull/3414
Fix search of local suggestions (#3417) Changelog: - fix: `search/completion` request with the position parameter. - fix: `refactoring/renameProject` request. Previously it did not take into account the library namespace (e.g. `local.`)
2022-04-26 15:06:48 +03:00
[3417]: https://github.com/enso-org/enso/pull/3417
Sum type info in suggestions DB (#3422) A draft of simple changes to the compiler to expose sum type information. Doesn't break the stdlib & at the same time allows for dropdowns. This is still broken, for example it doesn't handle exporting/importing types, only ones defined in the same module as the signature. Still, seems like a step in the right direction – please provide feedback. # Important Notes I've decided to make the variant info part of the type, not the argument – it is a property of the type logically. Also, I've pushed it as far as I'm comfortable – i.e. to the `SuggestionHandler` – I have no idea if this is enough to show in IDE? cc @4e6
2022-05-05 19:05:22 +03:00
[3422]: https://github.com/enso-org/enso/pull/3422
Delay conversion of Truffle function body nodes until the function is invoked (#3429) Most of the functions in the standard library aren't gonna be invoked during particular program execution. It makes no sense to build their Truffle AST for the functions that are not executing. Let's delay the construction of the tree until a function is first executed.
2022-05-05 13:53:49 +03:00
[3429]: https://github.com/enso-org/enso/pull/3429
Frgaal integration in sbt (#3421) * Initial integration with Frgaal in sbt Half-working since it chokes on generated classes from annotation processor. * Replace AutoService with ServiceProvider For reasons unknown AutoService would fail to initialize and fail to generate required builtin method classes. Hidden error message is not particularly revealing on the reason for that: ``` [error] error: Bad service configuration file, or exception thrown while constructing Processor object: javax.annotation.processing.Processor: Provider com.google.auto.service.processor.AutoServiceProcessor could not be instantiated ``` The sample records is only to demonstrate that we can now use newer Java features. * Cleanup + fix benchmark compilation Bench requires jmh classes which are not available because we obviously had to limit `java.base` modules to get Frgaal to work nicely. For now, we default to good ol' javac for Benchmarks. Limiting Frgaal to runtime for now, if it plays nicely, we can expand it to other projects. * Update CHANGELOG * Remove dummy record class * Update licenses * New line * PR review * Update legal review Co-authored-by: Radosław Waśko <radoslaw.wasko@enso.org>
2022-05-04 22:18:40 +03:00
[3421]: https://github.com/enso-org/enso/pull/3421
Debug Enso language in ChromeDev tools with --inspect option (#3432) Finally this pull request proposes `--inspect` option to allow [debugging of `.enso`](https://github.com/enso-org/enso/blob/e948f2535f71249daed647181324746613081d29/docs/debugger/README.md) in Chrome Developer Tools: ```bash enso$ ./built-distribution/enso-engine-0.0.0-dev-linux-amd64/enso-0.0.0-dev/bin/enso --inspect --run ./test/Tests/src/Data/Numbers_Spec.enso Debugger listening on ws://127.0.0.1:9229/Wugyrg9Nm4OUL9YhzdcElmLft71ayZW3LMUPCdPyNAY For help, see: https://www.graalvm.org/tools/chrome-debugger E.g. in Chrome open: devtools://devtools/bundled/js_app.html?ws=127.0.0.1:9229/Wugyrg9Nm4OUL9YhzdcElmLft71ayZW3LMUPCdPyNAY ``` copy the printed URL into chrome browser and you should see: ![obrazek](https://user-images.githubusercontent.com/26887752/167235327-8ad15fb2-96d4-4a0c-9e31-ed67ab46578b.png) One can also debug the `.enso` files in NetBeans or [VS Code with Apache Language Server extension](https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Extension+for+Visual+Studio+Code) just pass in special JVM arguments: ```bash enso$ JAVA_OPTS=-agentlib:jdwp=transport=dt_socket,server=y,address=8000 ./built-distribution/enso-engine-0.0.0-dev-linux-amd64/enso-0.0.0-dev/bin/enso --run ./test/Tests/src/Data/Numbers_Spec.enso Listening for transport dt_socket at address: 8000 ``` and then _Debug/Attach Debugger_. Once connected choose the _Toggle Pause in GraalVM Script_ button in the toolbar (the "G" button): ![obrazek](https://user-images.githubusercontent.com/26887752/167235598-98266c7e-beb5-406b-adc6-8167b3d1b453.png) and your execution shall stop on the next `.enso` line of code. This mode allows to debug both - the Enso code as well as Java code. Originally started as an attempt to write test in Java: * test written in Java * support for JUnit in `build.sbt` * compile Java with `-g` - so it can be debugged * Implementation of `StatementNode` - only gets created when `materialize` request gets to `BlockNode`
2022-05-10 11:55:08 +03:00
[3432]: https://github.com/enso-org/enso/pull/3432
Move Builtin Types and Methods to stdlib (#3363) This PR replaces hard-coded `@Builtin_Method` and `@Builtin_Type` nodes in Builtins with an automated solution that a) collects metadata from such annotations b) generates `BuiltinTypes` c) registers builtin methods with corresponding constructors. The main differences are: 1) The owner of the builtin method does not necessarily have to be a builtin type 2) You can now mix regular methods and builtin ones in stdlib 3) No need to keep track of builtin methods and types in various places and register them by hand (a source of many typos or omissions as it found during the process of this PR) Related to #181497846 Benchmarks also execute within the margin of error. ### Important Notes The PR got a bit large over time as I was moving various builtin types and finding various corner cases. Most of the changes however are rather simple c&p from Builtins.enso to the corresponding stdlib module. Here is the list of the most crucial updates: - `engine/runtime/src/main/java/org/enso/interpreter/runtime/builtin/Builtins.java` - the core of the changes. We no longer register individual builtin constructors and their methods by hand. Instead, the information about those is read from 2 metadata files generated by annotation processors. When the builtin method is encountered in stdlib, we do not ignore the method. Instead we lookup it up in the list of registered functions (see `getBuiltinFunction` and `IrToTruffle`) - `engine/runtime/src/main/java/org/enso/interpreter/runtime/callable/atom/AtomConstructor.java` has now information whether it corresponds to the builtin type or not. - `engine/runtime/src/main/scala/org/enso/compiler/codegen/RuntimeStubsGenerator.scala` - when runtime stubs generator encounters a builtin type, based on the @Builtin_Type annotation, it looks up an existing constructor for it and registers it in the provided scope, rather than creating a new one. The scope of the constructor is also changed to the one coming from stdlib, while ensuring that synthetic methods (for fields) also get assigned correctly - `engine/runtime/src/main/scala/org/enso/compiler/codegen/IrToTruffle.scala` - when a builtin method is encountered in stdlib we don't generate a new function node for it, instead we look it up in the list of registered builtin methods. Note that Integer and Number present a bit of a challenge because they list a whole bunch of methods that don't have a corresponding method (instead delegating to small/big integer implementations). During the translation new atom constructors get initialized but we don't want to do it for builtins which have gone through the process earlier, hence the exception - `lib/scala/interpreter-dsl/src/main/java/org/enso/interpreter/dsl/MethodProcessor.java` - @Builtin_Method processor not only generates the actual code fpr nodes but also collects and writes the info about them (name, class, params) to a metadata file that is read during builtins initialization - `lib/scala/interpreter-dsl/src/main/java/org/enso/interpreter/dsl/MethodProcessor.java` - @Builtin_Method processor no longer generates only (root) nodes but also collects and writes the info about them (name, class, params) to a metadata file that is read during builtins initialization - `lib/scala/interpreter-dsl/src/main/java/org/enso/interpreter/dsl/TypeProcessor.java` - Similar to MethodProcessor but handles @Builtin_Type annotations. It doesn't, **yet**, generate any builtin objects. It also collects the names, as present in stdlib, if any, so that we can generate the names automatically (see generated `types/ConstantsGen.java`) - `engine/runtime/src/main/java/org/enso/interpreter/node/expression/builtin` - various classes annotated with @BuiltinType to ensure that the atom constructor is always properly registered for the builitn. Note that in order to support types fields in those, annotation takes optional `params` parameter (comma separated). - `engine/runtime/src/bench/scala/org/enso/interpreter/bench/fixtures/semantic/AtomFixtures.scala` - drop manual creation of test list which seemed to be a relict of the old design
2022-05-05 21:18:06 +03:00
[3363]: https://github.com/enso-org/enso/pull/3363
Generate BuiltinMethods from simple method and constructor signatures (#3444) A low-hanging fruit where we can automate the generation of many @BuiltinMethod nodes simply from the runtime's methods signatures. This change introduces another annotation, @Builtin, to distinguish from @BuiltinType and @BuiltinMethod processing. @Builtin processing will always be the first stage of processing and its output will be fed to the latter. Note that the return type of Array.length() is changed from `int` to `long` because we probably don't want to add a ton of specializations for the former (see comparator nodes for details) and it is fine to cast it in a small number of places. Progress is visible in the number of deleted hardcoded classes. This is an incremental step towards #181499077. # Important Notes This process does not attempt to cover all cases. Not yet, at least. We only handle simple methods and constructors (see removed `Array` boilerplate methods).
2022-05-12 11:42:00 +03:00
[3444]: https://github.com/enso-org/enso/pull/3444
Replace Rope with CharSequence when building suggestions (#3453) PR addresses an issue when during the initial compilation the `EnsureCompiledJob` depends too much time building the `LineView` of ropes. Replacing the `Rope` with `CharSequence` in the compilation job reduces total time building the suggestions from ~600 ms to ~200 ms. #### Before ![2022-05-13-160549_1310x120_scrot](https://user-images.githubusercontent.com/357683/168289736-fe8983ef-9bcc-4df0-bcd2-881bc2949773.png) #### After ![2022-05-13-160609_1303x123_scrot](https://user-images.githubusercontent.com/357683/168289741-3326603d-8183-4925-b995-435655d6c8be.png) [context-registry-npss.zip](https://github.com/enso-org/enso/files/8687294/context-registry-npss.zip)
2022-05-16 09:47:35 +03:00
[3453]: https://github.com/enso-org/enso/pull/3453
Part 2 of system for builtin objects (#3454) This is the 2nd part of DSL improvements that allow us to generate a lot of builtins-related boilerplate code. - [x] generate multiple method nodes for methods/constructors with varargs - [x] expanded processing to allow for @Builtin to be added to classes and and generate @BuiltinType classes - [x] generate code that wraps exceptions to panic via `wrapException` annotation element (see @Builtin.WrapException` Also rewrote @Builtin annotations to be more structured and introduced some nesting, such as @Builtin.Method or @Builtin.WrapException. This is part of incremental work and a follow up on https://github.com/enso-org/enso/pull/3444. # Important Notes Notice the number of boilerplate classes removed to see the impact. For now only applied to `Array` but should be applicable to other types.
2022-05-19 13:43:47 +03:00
[3454]: https://github.com/enso-org/enso/pull/3454
Update profiling CLI arguments (#3461)
2022-05-24 16:01:26 +03:00
[3461]: https://github.com/enso-org/enso/pull/3461
Avoid needless concatenations of warning/error messages (#3465) While investigating [#182234656](https://www.pivotaltracker.com/n/projects/2539304/stories/182234656) I've noticed that `GatherDiagnostics` calls `distinctBy` and uses `message` string. However such string has to be composed and that takes time: ![image](https://user-images.githubusercontent.com/26887752/169638644-cf7dd826-1016-402b-842a-fc27a77a64e1.png) This PR eliminates the need for concatenation by associating each `Diagnostic` with an array of `keys` used to compute `equals` and `hashCode`.
2022-05-24 08:16:36 +03:00
[3465]: https://github.com/enso-org/enso/pull/3465
Towards a full-blown builtins DSL (part 3) (#3471) Auto-generate all builtin methods for builtin `File` type from method signatures. Similarly, for `ManagedResource` and `Warning`. Additionally, support for specializations for overloaded and non-overloaded methods is added. Coverage can be tracked by the number of hard-coded builtin classes that are now deleted. ## Important notes Notice how `type File` now lacks `prim_file` field and we were able to get rid off all of those propagating method calls without writing a single builtin node class. Similarly `ManagedResource` and `Warning` are now builtins and `Prim_Warnings` stub is now gone.
2022-06-13 14:48:34 +03:00
[3471]: https://github.com/enso-org/enso/pull/3471
Enso Integration with Ideal Graph Visualizer (#3533) This PR adds sources for Enso language support in IGV (and NetBeans). The support is based on TextMate grammar shown in the editor and registration of the Enso language so IGV can find it. Then this PR adds new GitHub Actions workflow file to build the project using Maven.
2022-06-23 07:43:49 +03:00
[3533]: https://github.com/enso-org/enso/pull/3533
Short-circuiting || and && (#3492) Short-circuiting || and && is typically taken for granted by users of other PLs. This change makes it happen for Enso. Related to https://www.pivotaltracker.com/story/show/182261401
2022-06-02 19:58:38 +03:00
[3492]: https://github.com/enso-org/enso/pull/3492
Add background suggestions processing (#3493) PR implements background job processing. #### Before ![2022-05-30-084652_1158x123_scrot](https://user-images.githubusercontent.com/357683/170936632-06413b0f-fb6c-4c31-89ca-a3fbd6f7293e.png) #### After ![2022-05-30-084634_1118x117_scrot](https://user-images.githubusercontent.com/357683/170936626-9ed21b5c-f44e-4878-bdd8-4866dfeba060.png) After moving the suggestions building out of the compilation job, the initial compilation time has been reduced by 25% (before ~11 seconds, after ~8 seconds). [language-server.npss.zip](https://github.com/enso-org/enso/files/8796281/language-server.npss.zip) Changelog: - Implement background jobs executor - Implement jobs for suggestion processing - Move suggestion processing out of the compilation job - Update handling of expected messages in various runtime tests. The runtime tests execution time was improved by a couple of minutes
2022-06-01 12:39:48 +03:00
[3493]: https://github.com/enso-org/enso/pull/3493
Keep the components order (#3505) PR ensures that the component groups are returned in the same order that the packages were loaded.
2022-06-03 21:45:56 +03:00
[3505]: https://github.com/enso-org/enso/pull/3505
Minor compilation improvements (#3512) Drop `Core` implementation (replacement for IR) as it (sadly) looks increasingly unlikely this effort will be continued. Also, it heavily relies on implicits which increases some compilation time (~1sec from `clean`) Related to https://www.pivotaltracker.com/story/show/182359029
2022-06-07 17:48:50 +03:00
[3512]: https://github.com/enso-org/enso/pull/3512
Substitute this with self (#3524) A semi-manual s/this/self appied to the whole standard library. Related to https://www.pivotaltracker.com/story/show/182328601 In the compiler promoted to use constants instead of hardcoded `this`/`self` whenever possible. # Important Notes The PR **does not** require explicit `self` parameter declaration for methods as this part of the design is still under consideration.
2022-06-21 13:53:52 +03:00
[3524]: https://github.com/enso-org/enso/pull/3524
introduce a micro stdlib for testing (#3531) This introduces a tiny alternative to our stdlib, that can be used for testing the interpreter. There are 2 main advantages of such a solution: 1. Performance: on my machine, `runtime-with-intstruments/test` drops from 146s to 65s, while `runtime/test` drops from 165s to 51s. >6 mins total becoming <2 mins total is awesome. This alone means I'll drink less coffee in these breaks and will be healthier. 2. Better separation of concepts – currently working on a feature that breaks _all_ enso code. The dependency of interpreter tests on the stdlib means I have no means of incremental testing – ALL of stdlib must compile. This is horrible, rendered my work impossible, and resulted in this PR.
2022-06-16 13:25:24 +03:00
[3531]: https://github.com/enso-org/enso/pull/3531
Add command for changing expression value (#3562) Implement `text/applyExpressionValue` command.
2022-07-13 18:59:47 +03:00
[3562]: https://github.com/enso-org/enso/pull/3562
Remove 'here' and make method name resolution case-sensitive (#3538) Modified UppercaseNames to now resolve methods without an explicit `here` to point to the current module. `here` was also often used instead of `self` which was allowed by the compiler. Therefore UppercaseNames pass is now GlobalNames and does some extra work - it translated method calls without an explicit target into proper applications. # Important Notes There was a long-standing bug in scopes usage when compiling standalone expressions. This resulted in AliasAnalysis generating incorrect graphs and manifested itself only in unit tests and when running `eval`, thus being a bit hard to locate. See `runExpression` for details. Additionally, method name resolution is now case-sensitive. Obsolete passes like UndefinedVariables and ModuleThisToHere were removed. All tests have been adapted.
2022-07-07 13:31:06 +03:00
[3538]: https://github.com/enso-org/enso/pull/3538
Use Vector.from_polyglot_array to make Vectors backed by polyglot arrays (#3628) Use Proxy_Polyglot_Array as a proxy for polyglot arrays, thus unifying the way the underlying array is accessed in Vector. Used the opportunity to cleanup builtin lookup, which now actually respects what is defined in the body of @Builtin_Method annotation. Also discovered that polyglot null values (in JS, Python and R) were leaking to Enso. Fixed that by doing explicit translation to `Nothing`. https://www.pivotaltracker.com/story/show/181123986
2022-08-24 00:13:16 +03:00
[3569]: https://github.com/enso-org/enso/pull/3569
[3578]: https://github.com/enso-org/enso/pull/3578
Use Rust Parser from Java instead of AST.scala (#3611)
2022-11-13 09:22:02 +03:00
[3611]: https://github.com/enso-org/enso/pull/3611
Enable caching in visualization functions (#3618) PR allows to attach metod pointers as a visualization expressions. This way it allows to attach a runtime instrument that enables caching of intermediate expressions. # Important Notes :information_source: API is backward compatible. To attach the visualization with caching support, the same `executionContext/attachVisualisation` method is used, but `VisualisationConfig` message should contain the message pointer. While `VisualisationConfiguration` message has changed, the language server accepts both new and old formats to keep visualisations working in IDE. #### Old format ```json { "executionContextId": "UUID", "visualisationModule": "local.Unnamed.Main", "expression": "x -> x.to_text" } ``` #### New format ```json { "executionContextId": "UUID", "expression": { "module": "local.Unnamed.Main", "definedOnType": "local.Unnamed.Main", "name": "encode" } } ```
2022-08-10 15:01:33 +03:00
[3618]: https://github.com/enso-org/enso/pull/3618
[3608]: https://github.com/enso-org/enso/pull/3608
Support module imports using a qualified name (#3608) This change allows for importing modules using a qualified name and deals with any conflicts on the way. Given a module C defined at `A/B/C.enso` with ``` type C type C a ``` it is now possible to import it as ``` import project.A ... val x = A.B.C 10 ``` Given a module located at `A/B/C/D.enso`, we will generate intermediate, synthetic, modules that only import and export the successor module along the path. For example, the contents of a synthetic module B will look like ``` import <namespace>.<pkg-name>.A.B.C export <namespace>.<pkg-name>.A.B.C ``` If module B is defined already by the developer, the compiler will _inject_ the above statements to the IR. Also removed the last elements of some lowercase name resolution that managed to survive recent changes (`Meta.Enso_Project` would now be ambiguous with `enso_project` method). Finally, added a pass that detects shadowing of the synthetic module by the type defined along the path. We print a warning in such a situation. Related to https://www.pivotaltracker.com/n/projects/2539304 # Important Notes There was an additional request to fix the annoying problem with `from` imports that would always bring the module into the scope. The changes in stdlib demonstrate how it is now possible to avoid the workaround of ``` from X.Y.Z as Z_Module import A, B ``` (i.e. `as Z_Module` part is almost always unnecessary).
2022-07-29 17:19:07 +03:00
[3608]: https://github.com/enso-org/enso/pull/3608
Update Scala to 2.13.8 (#3631) Update Scala compiler and libraries.
2022-08-08 22:32:55 +03:00
[3631]: https://github.com/enso-org/enso/pull/3631
Allow for importing methods (#3633) Importing individual methods didn't work as advertised because parser would allow them but later drop that information. This slipped by because we never had mixed atoms and methods in stdlib. # Important Notes Added some basic tests but we need to ensure that the new parser allows for this. @jdunkerley will be adding some changes to stdlib that will be testing this functionality as well.
2022-08-05 19:25:51 +03:00
[3633]: https://github.com/enso-org/enso/pull/3633
Support Autosave for open buffers (#3637) This change adds Autosave action for open buffers. The action is scheduled after every edit request and is cancelled by every explicit save file request, if necessary. Successful autosave also notifies any active clients of the buffer. Related to https://www.pivotaltracker.com/story/show/182721656 # Important Notes WIP
2022-08-11 14:45:12 +03:00
[3637]: https://github.com/enso-org/enso/pull/3637
New set function, parse a column (#4097) - New `set` function design - takes a `Column` and works with that more easily and supports control of `Set_Mode`. - New simple `parse` API on `Column`. - Separated expression support for `filter` to new `filter_by_expression` on `Table`. - New `compute` function allowing creation of a column from an expression. - Added case sensitivity argument to `Column` based on `starts_with`, `ends_with` and `contains`. - Added case sensitivity argument to `Filter_Condition` for `Starts_With`, `Ends_With`, `Contains` and `Not_Contains`. - Fixed the issue in JS Table visualisation where JavaScript date was incorrectly set. - Some dynamic dropdown expressions - experimenting with ways to use them. - Fixed issue with `.pretty` that wasn't escaping `\`. - Changed default Postgres DB to `postgres`. - Fixed SQLite support for starts_with, ends_with and contains to be consistent (using GLOB not LIKE).
2023-01-31 23:48:16 +03:00
[3638]: https://github.com/enso-org/enso/pull/3638
Remove `Array.set_at` (#3634) Implements https://www.pivotaltracker.com/story/show/182879865 # Important Notes Note that removing `set_at` still does not make our arrays fully immutable - `Array.copy` can still be used to mutate them.
2022-08-26 12:34:33 +03:00
[3641]: https://github.com/enso-org/enso/pull/3641
Builtin Date_Time, Time_Of_Day, Zone (#3658) * Builtin Date_Time, Time_Of_Day, Zone Improved polyglot support for Date_Time (formerly Time), Time_Of_Day and Zone. This follows the pattern introduced for Enso Date. Minor caveat - in tests for Date, had to bend a lot for JS Date to pass. This is because JS Date is not really only a Date, but also a Time and Timezone, previously we just didn't consider the latter. Also, JS Date does not deal well with setting timezones so the trick I used is to first call foreign function returning a polyglot JS Date, which is converted to ZonedDateTime and only then set the correct timezone. That way none of the existing tests had to be changes or special cased. Additionally, JS deals with milliseconds rather than nanoseconds so there is loss in precision, as noted in Time_Spec. * Add tests for Java's LocalTime * changelog * Make date formatters in table happy * PR review, add more tests for zone * More tests and fixed a bug in column reader Column reader didn't take into account timezone but that was a mistake since then it wouldn't map to Enso's Date_Time. Added tests that check it now. * remove redundant conversion * Update distribution/lib/Standard/Base/0.0.0-dev/src/Data/Time.enso Co-authored-by: Radosław Waśko <radoslaw.wasko@enso.org> * First round of addressing PR review * don't leak java exceptions in Zone * Move Date_Time to top-level module * PR review Co-authored-by: Radosław Waśko <radoslaw.wasko@enso.org> Co-authored-by: Jaroslav Tulach <jaroslav.tulach@enso.org>
2022-08-24 13:31:29 +03:00
[3658]: https://github.com/enso-org/enso/pull/3658
Get rid of free-floating atoms. Everything has a type now! (#3671) This is a step towards the new language spec. The `type` keyword now means something. So we now have ``` type Maybe a Some (from_some : a) None ``` as a thing one may write. Also `Some` and `None` are not standalone types now – only `Maybe` is. This halfway to static methods – we still allow for things like `Number + Number` for backwards compatibility. It will disappear in the next PR. The concept of a type is now used for method dispatch – with great impact on interpreter code density. Some APIs in the STDLIB may require re-thinking. I take this is going to be up to the libraries team – some choices are not as good with a semantically different language. I've strived to update stdlib with minimal changes – to make sure it still works as it did. It is worth mentioning the conflicting constructor name convention I've used: if `Foo` only has one constructor, previously named `Foo`, we now have: ``` type Foo Foo_Data f1 f2 f3 ``` This is now necessary, because we still don't have proper statics. When they arrive, this can be changed (quite easily, with SED) to use them, and figure out the actual convention then. I have also reworked large parts of the builtins system, because it did not work at all with the new concepts. It also exposes the type variants in SuggestionBuilder, that was the original tiny PR this was based on. PS I'm so sorry for the size of this. No idea how this could have been smaller. It's a breaking language change after all.
2022-08-31 01:54:53 +03:00
[3671]: https://github.com/enso-org/enso/pull/3671
Print result of main (if not Nothing) (#3696) The goal of this request is to simplify hello world and other trivial Enso programs. No need to learn any standard library functions, enough to write: ``` main = "Hello World!" ``` and the result is going to be printed: ```bash enso$ ./built-distribution/enso-engine-0.0.0-dev-linux-amd64/enso-0.0.0-dev/bin/enso --run hello.enso 'Hello World!' ``` the result is only printed, if it is not `Nothing`. E.g. if the last statement is `IO.print ...` (which returns `Nothing`), then no value is printed at the end by the launcher.
2022-09-12 18:37:46 +03:00
[3696]: https://github.com/enso-org/enso/pull/3696
Engine should send notification about node status (#3729) When nodes get invalidated in the cache, they have to be recomputed. Let the IDE know which of the nodes are pending by sending `Api.ExpressionUpdate.Payload.Pending` message. # Important Notes This PR introduces new `Api.ExpressionUpdate.Payload.Pending` message. This message is delivered before re-computation of nodes. Later `Api.ExpressionUpdate.Payload.Value` or other is sent to notify the IDE that a value for given node is available. Trivial implementation of of the `Api.ExpressionUpdate.Payload.Pending` message in the IDE is provided by this PR to (improperly) visualize pending node status - further improvements needed in follow up PRs.
2022-09-28 15:35:12 +03:00
[3703]: https://github.com/enso-org/enso/pull/3703
[3710]: https://github.com/enso-org/enso/pull/3710
[3729]: https://github.com/enso-org/enso/pull/3729
Wip/mk/statics (#3740) Makes statics static. A type and its instances have different methods defined on them, as it should be. Constructors are now scoped in types, and can be imported/exported. # Important Notes The method of fixing stdlib chosen here is to just not. All the conses are exported to make all old code work. All such instances are marked with `TODO Dubious constructor export` so that it can be found and fixed.
2022-09-27 17:23:06 +03:00
[3740]: https://github.com/enso-org/enso/pull/3740
Static, but instance, but static (#3764) Adds the ability to write `Foo.method (Mk_Foo 123)` as a synonym of `(Mk_Foo 123).method` because Rust.
2022-10-10 22:28:33 +03:00
[3764]: https://github.com/enso-org/enso/pull/3764
By-type pattern matching (#3742) This change brings by-type pattern matching to Enso. One can pattern match on Enso types as well as on polyglot types. For example, ``` case x of _ : Integer -> ... _ : Text -> ... _ -> ... ``` as well as Java's types ``` case y of _ : ArrayList -> ... _ : List -> ... _ : AbstractList -> ... _ -> .. ``` It is no longer possible to match a value with a corresponding type constructor. For example ``` case Date.now of Date -> ... ``` will no longer match and one should match on the type (`_ : Date`) instead. ``` case Date of Date -> ... ``` is fine though, as requested in the ticket. The change required further changes to `type_of` logic which wasn't dealing well with polyglot values. Implements https://www.pivotaltracker.com/story/show/183188846 # Important Notes ~I discovered late in the game that nested patterns involving type patterns, such as `Const (f : Foo) tail -> ...` are not possible due to the old parser logic. I would prefer to add it in a separate PR because this one is already getting quite large.~ This is now supported!
2022-10-04 12:23:58 +03:00
[3742]: https://github.com/enso-org/enso/pull/3742
Fix for perf degradation in method calls on polyglot arrays (#3781)
2022-10-10 19:35:38 +03:00
[3781]: https://github.com/enso-org/enso/pull/3781
Don't add module's builtins to the scope of a builtin type (#3791) It appears that we were always adding builtin methods to the scope of the module and the builtin type that shared the same name. This resulted in some methods being accidentally available even though they shouldn't. This change treats differently builtins of types and modules and introduces auto-registration feature for builtins. By default all builtin methods are registered with a type, unless explicitly defined in the annotation property. Builtin methods that are auto-registered do not have to be explicitly defined and are registered with the underlying type. Registration correctly infers the right type, depending whether we deal with static or instance methods. Builtin methods that are not auto-registered have to be explicitly defined **always**. Modules' builtin methods are the prime example. # Important Notes Builtins now carry information whether they are static or not (inferred from the lack of `self` parameter). They also carry a `autoRegister` property to determine if a builtin method should be automatically registered with the type.
2022-11-16 13:23:52 +03:00
[3791]: https://github.com/enso-org/enso/pull/3791
Missing foreign language generates proper Enso error. (#3798) Trying to invoke a foreign method with non-installed language (either not enabled in the Truffle `Context`, or not installed in the GraalVM distribution) results in `Polyglot_Error`, rather than crashing the entire engine.
2022-10-17 12:59:31 +03:00
[3798]: https://github.com/enso-org/enso/pull/3798
Allow multiple exports of the same module (#3897) Previously, when exporting the same module multiple times only the first statement would count and the rest would be discarded by the compiler. This change allows for multiple exports of the same module e.g., ``` export project.F1 from project.F1 export foo ``` Multiple exports may however lead to conflicts when combined with hiding names. Added logic in `ImportResolver` to detect such scenarios. This fixes https://www.pivotaltracker.com/n/projects/2539304/stories/183092447 # Important Notes Added a bunch of scenarios to simulate pos and neg results.
2022-11-23 14:40:59 +03:00
[3810]: https://github.com/enso-org/enso/pull/3810
Move logic calculating the index in Vector.at to a builtin method to make the performance of Vector to be on par with Array (#3811) The main culprit of a Vector slowdown (when compared to Array) was the normalization of the index when accessing the elements. Turns out that the Graal was very persistent on **not** inlining that particular fragment and that was degrading the results in benchmarks. Being unable to force it to do it (looks like a combination of thunk execution and another layer of indirection) we resorted to just moving the normalization to the builtin method. That makes Array and Vector perform roughly the same. Moved all handling of invalid index into the builtin as well, simplifying the Enso implementation. This also meant that `Vector.unsafe_at` is now obsolete. Additionally, added support for negative indices in Array, to behave in the same way as for Vector. # Important Notes Note that this workaround only addresses this particular perf issue. I'm pretty sure we will have more of such scenarios. Before the change `averageOverVector` benchmark averaged around `0.033 ms/op` now it does consistently `0.016 ms/op`, similarly to `averageOverArray`.
2022-10-20 15:50:44 +03:00
[3811]: https://github.com/enso-org/enso/pull/3811
Accept Array-like objects seamlessly in builtins (#3817) Most of the time, rather than defining the type of the parameter of the builtin, we want to accept every Array-like object i.e. Vector, Array, polyglot Array etc. Rather than writing all possible combinations, and likely causing bugs on the way anyway as we already saw, one should use `CoerceArrayNode` to convert to Java's `Object[]`. Added various test cases to illustrate the problem.
2022-10-25 15:44:48 +03:00
[3817]: https://github.com/enso-org/enso/pull/3817
Initialize Builtins at Native Image build time (#3821) Moved loading of Builtin Types and Methods to a static initializer. That way the information is available at Native Image build time and one does not have to update a corresponding entry in `reflect-config` which would be a real pain when we start using it in anger. Fixes https://www.pivotaltracker.com/story/show/183374932
2022-10-25 21:28:10 +03:00
[3821]: https://github.com/enso-org/enso/pull/3821
Allow multiple exports of the same module (#3897) Previously, when exporting the same module multiple times only the first statement would count and the rest would be discarded by the compiler. This change allows for multiple exports of the same module e.g., ``` export project.F1 from project.F1 export foo ``` Multiple exports may however lead to conflicts when combined with hiding names. Added logic in `ImportResolver` to detect such scenarios. This fixes https://www.pivotaltracker.com/n/projects/2539304/stories/183092447 # Important Notes Added a bunch of scenarios to simulate pos and neg results.
2022-11-23 14:40:59 +03:00
[3828]: https://github.com/enso-org/enso/pull/3828
Split Atom suggestion entry to Type and Constructor (#3835) Changelog: - update: split `Atom` suggestion to `Type` and `Constructor` - update: gui API - update: JSONRPC doc
2022-11-02 12:53:40 +03:00
[3835]: https://github.com/enso-org/enso/pull/3835
Allow conversion of EnsoBigInteger to double (#3865) Make sure any Enso number (including `EnsoBigInteger`) can be passed to Java via Truffle interop and used on the Java side.
2022-11-24 13:00:16 +03:00
[3865]: https://github.com/enso-org/enso/pull/3865
Upgrade to GraalVM 22.3.0 (#3663) Upgrading to GraalVM 22.3.0. # Important Notes - Removed all deprecated `FrameSlot`, and replaced them with frame indexes - integers. - Add more information to `AliasAnalysis` so that it also gathers these indexes. - Add quick build mode option to `native-image` as default for non-release builds - `graaljs` and `native-image` should now be downloaded via `gu` automatically, as dependencies. - Remove `engine-runner-native` project - native image is now build straight from `engine-runner`. - We used to have `engine-runner-native` without `sqldf` in classpath as a workaround for an internal native image bug. - Fixed chrome inspector integration, such that it shows values of local variables both for current stack frame and caller stack frames. - There are still many issues with the debugging in general, for example, when there is a polyglot value among local variables, a `NullPointerException` is thrown and no values are displayed. - Removed some deprecated `native-image` options - Remove some deprecated Truffle API method calls.
2022-11-23 17:30:48 +03:00
[3663]: https://github.com/enso-org/enso/pull/3663
[3810]: https://github.com/enso-org/enso/pull/3810
Allow multiple exports of the same module (#3897) Previously, when exporting the same module multiple times only the first statement would count and the rest would be discarded by the compiler. This change allows for multiple exports of the same module e.g., ``` export project.F1 from project.F1 export foo ``` Multiple exports may however lead to conflicts when combined with hiding names. Added logic in `ImportResolver` to detect such scenarios. This fixes https://www.pivotaltracker.com/n/projects/2539304/stories/183092447 # Important Notes Added a bunch of scenarios to simulate pos and neg results.
2022-11-23 14:40:59 +03:00
[3844]: https://github.com/enso-org/enso/pull/3844
Project save backed by git (#3851) This change adds support for Version Controlled projects in language server. Version Control supports operations: - `init` - initialize VCS for a project - `save` - commit all changes to the project in VCS - `restore` - ability to restore project to some past `save` - `status` - show the status of the project from VCS' perspective - `list` - show a list of requested saves # Important Notes Behind the scenes, Enso's VCS uses git (or rather [jGit](https://www.eclipse.org/jgit/)) but nothing stops us from using a different implementation as long as it conforms to the establish API.
2022-11-14 20:32:39 +03:00
[3851]: https://github.com/enso-org/enso/pull/3851
Unboxed atoms (#3862) Introduces unboxed (and arity-specialized) storage schemes for Atoms. It results in improvements both in memory consumption and runtime. Memory wise: instead of using an array, we now use object fields. We also enable unboxing. This cuts a good few pointers in an unboxed object. E.g. a quadruple of integers is now 64 bytes (4x8 bytes for long fields + 16 bytes for layout and constructor pointers + 16 bytes for a class header). It used to be 168 bytes (4x24 bytes for boxed Longs + 16 bytes for array header + 32 bytes for array contents + 8 bytes for constructor ptr + 16 bytes for class header), so we're saving 104 bytes a piece. In the least impressive scenarios (all-boxed fields) we're saving 8 bytes per object (saving 16 bytes for array header, using 8 bytes for the new layout field). In the most-benchmarked case (list of longs), we save 32 bytes per cons-cell. Time wise: All list-summing benchmarks observe a ~2x speedup. List generation benchmarks get ~25x speedups, probably both due to less GC activity and better allocation characteristics (only allocating one object per Cons, rather than Cons + Object[] for fields). The "map-reverse" family gets a neat 10x speedup (part of the work is reading, which is 2x faster, the other is allocating, which is now 25x faster, we end up with 10x when combined).
2023-01-24 16:03:06 +03:00
[3862]: https://github.com/enso-org/enso/pull/3862
Allow multiple exports of the same module (#3897) Previously, when exporting the same module multiple times only the first statement would count and the rest would be discarded by the compiler. This change allows for multiple exports of the same module e.g., ``` export project.F1 from project.F1 export foo ``` Multiple exports may however lead to conflicts when combined with hiding names. Added logic in `ImportResolver` to detect such scenarios. This fixes https://www.pivotaltracker.com/n/projects/2539304/stories/183092447 # Important Notes Added a bunch of scenarios to simulate pos and neg results.
2022-11-23 14:40:59 +03:00
[3897]: https://github.com/enso-org/enso/pull/3897
Import modules' extension methods only with unqualified import statements (#3906) # Important Notes Note that one cannot ``` import Standard.Table as Table_Module ``` because of the 2-component name restriction that gets desugared to `Standard.Table.Main` and we have to write ``` import Standard.Table.Main as Table_Module ``` in a few places. Once we move `Json.to_table` extension this can be improved.
2022-12-01 13:13:34 +03:00
[3906]: https://github.com/enso-org/enso/pull/3906
Allow arbitrary expression evaluation in chromeinspector (#3941) Allow arbitrary expression evaluation in the chromeinspector console. Moreover, allow modifications of any variable in any stack frame. # Important Notes - Implement inline parsing in `EnsoLanguage.parse(InlineParsingRequest)`. - Debugging experience is affected by this [bug in Truffle](https://github.com/oracle/graal/issues/5513), which causes NPEs when a host object gets into chromeinspector. I tried to implement a workaround, but it does not work all the time. Nevertheless, it should not matter that much - if there is a NPE in the debugger, you can just ignore it, as it should be concealed in the debugger and should not be propagted outside. See comments in the `docs/debugger`.
2022-12-08 02:02:42 +03:00
[3941]: https://github.com/enso-org/enso/pull/3941
Don't export polyglot symbols (#3915) By default all polyglot symbols that have been imported were always exported. This means that importing a module that had some polyglot imports brought them into the scope automatically. This didn't follow our desired semantics. Fixes task 3 in https://www.pivotaltracker.com/story/show/183833055.
2022-11-28 22:11:31 +03:00
[3915]: https://github.com/enso-org/enso/pull/3915
from/all import must not include module in name resolution (#3931) It appears that when were doing `from XYZ import all` the module `XYZ` was also being taken into account during name resolution. This was unfortunate and became problematic when one had a type with the same name defined in it. During pattern matching one could not simply do ``` from XYZ import all ... case ... of _ : XYZ -> ... ``` since the compiler would complain that we try to pattern match on a type but give it a module. The module is now excluded from the name resolution, when importing everything from the module. It appears that this "feature" was used in a number of our tests, so they had to be adapted. This fixes task 4 in https://www.pivotaltracker.com/story/show/183833055
2022-11-30 19:28:57 +03:00
[3931]: https://github.com/enso-org/enso/pull/3931
Vector should preserve warnings (#3938) * Sequence literal (Vector) should preserve warnings When Vector was created via a sequence literal, we simply dropped any associated any warnings associated with it. This change propagates Warnings during the creation of the Vector. Ideally, it would be sufficient to propagate warnings from the individual elements to the underlying storage but doesn't go well with `Vector.fromArray`. * update changelog * Array-like structures preserver warnings Added a WarningsLibrary that exposes `hasWarnings` and `getWarnings` messages. That way we can have a single storage that defines how to extract warnings from an Array and the others just delegate to it. This simplifies logic added to sequence literals to handle warnings. * Ensure polyglot method calls are warning-free Since warnings are no longer automatically extracted from Array-like structures, we delay the operation until an actual polyglot method call is performed. Discovered a bug in `Warning.detach_selected_warnings` which was missing any usage or tests. * nits * Support multi-dimensional Vectors with warnings * Propagate warnings from case branches * nit * Propagate all vector warnings when reading element Previously, accessing an element of an Array-like structure would only return warnings of that element or of the structure itself. Now, accessing an element also returns warnings from all its elements as well.
2022-12-07 13:10:11 +03:00
[3938]: https://github.com/enso-org/enso/pull/3938
Enso.getMetaObject, Type.isMetaInstance and Meta.is_a consolidation (#3949) Implements `getMetaObject` and related messages from Truffle interop for Enso values and types. Turns `Meta.is_a` into builtin and re-uses the same functionality. # Important Notes Adds `ValueGenerator` testing infrastructure to provide unified access to special Enso values and builtin types that can be reused by other tests, not just `MetaIsATest` and `MetaObjectTest`.
2022-12-22 11:00:06 +03:00
[3949]: https://github.com/enso-org/enso/pull/3949
Add executionContext/interrupt API command (#3952) Implement the `executionContext/interrupt` API command that forcibly stops the program execution.
2022-12-08 03:04:46 +03:00
[3952]: https://github.com/enso-org/enso/pull/3952
Convert Any.== to a builtin (#3956) `Any.==` is a builtin method. The semantics is the same as it used to be, except that we no longer assume `x == y` iff `Meta.is_same_object x y`, which used to be the case and caused failures in table tests. # Important Notes Measurements from `EqualsBenchmarks` shows that the performance of `Any.==` for recursive atoms increased by roughly 20%, and the performance for primitive types stays roughly the same.
2022-12-30 00:20:00 +03:00
[3956]: https://github.com/enso-org/enso/pull/3956
Simplify exception handling for polyglot exceptions (#3981) This removes the special handling of polyglot exceptions and allows matching on Java exceptions in the same way as for any other types. `Polyglot_Error`, `Panic.catch_java` and `Panic.catch_primitive` are gone The change mostly deals with the backslash of removing `Polyglot_Error` and two `Panic` methods. `Panic.catch` was implemented as a builtin instead of delegating to `Panic.catch_primitive` builtin that is now gone. This fixes https://www.pivotaltracker.com/story/show/182844611
2022-12-19 22:16:43 +03:00
[3981]: https://github.com/enso-org/enso/pull/3981
Simplify compilation of nested patterns (#4005) `NestedPatternMatch` pass desugared complex patterns in a very inefficient way resulting in an exponential generation of the number of `case` IR (and Truffle) nodes. Every failed nested pattern would copy all the remaining patterns of the original case expression, in a desugared form. While the execution itself of such deeply nested `case` expression might not have many problems, the time spent in compilation phases certainly was a blocker. This change desugars deeply nested into individual cases with a fallthrough logic. However the fallthrough logic is implemented directly in Truffle nodes, rather than via IR. That way we can generate much simpler IR for nested patterns. Consider a simple case of ``` case x of Cons (Cons a b) Nil -> a + b Cons a Nil -> a _ -> 0 ``` Before the change, the compiler would generate rather large IR even for those two patterns: ``` case x of Cons w y -> case w of Cons a b -> case y of Nil -> a + b _ -> case x of Cons a z -> case z of Nil -> a _ -> case x of _ -> 0 _ -> 0 _ -> case x of Cons a z -> case z of Nil -> a _ -> case x of _ -> 0 _ -> 0 Cons a z -> case z of Nil -> a _ -> case x of _ -> 0 _ -> 0 ``` Now we generate simple patterns with fallthrough semantics and no catch-all branches: ``` case x of Cons w y -> case w of Cons a b -> case y of ## fallthrough on failed match ## Nil -> a + b ## fallthrough on failed match ## Cons a z -> case z of Nil -> a ## fallthrough on failed match ## _ -> 0 ``` # Important Notes If you wonder how much does it improve, then @radeusgd's example in https://www.pivotaltracker.com/story/show/183971366/comments/234688327 used to take at least 8 minutes to compile and run. Now it takes 5 seconds from cold start. Also, the example in the benchmark includes compilation time on purpose (that was the main culprit of the slowdown). For the old implementation I had to kill it after 15 minutes as it still wouldn't finish a single compilation. Now it runs 2 seconds or less. Bonus points: This PR will also fix problem reported in https://www.pivotaltracker.com/story/show/184071954 (duplicate errors for nested patterns)
2022-12-30 13:56:27 +03:00
[4005]: https://github.com/enso-org/enso/pull/4005
IGV can jump to JMH sources & more (#4008) Improvements to behavior and visual appearance of IGV Enso integration.
2022-12-30 08:30:32 +03:00
[4008]: https://github.com/enso-org/enso/pull/4008
Basic VSCode support for Enso language and development (#4014) Basic VSCode support for Enso language and development # Important Notes See the [building instructions](https://github.com/enso-org/enso/pull/4014/files#diff-1f944b52bce988a17f27b2cdd35e0efe16a1df8b86ee6ced94c0a286033f1ab3R154).
2023-01-06 17:18:20 +03:00
[4014]: https://github.com/enso-org/enso/pull/4014
Sync file system and language server after restore (#4020) VCS restore operation was correctly restoring the state of projects to the requested commit. Unfortunately, after the operation file system was becoming out-of-sync with language server's buffers (and IDE's content versions). A few important changes are introduced here that complicate the interaction between components: 1) `vcs restore` returns an actual diff between the current state and the requested commit 2) the response is forwarded to buffer registry first rather than to the client 3) the diff is used to identify appropriate collaborative editors and notify them about the need to reload buffers from file system 4) all clients of affected open buffers are notified of the change via `text/didChange` notification. If a file was removed and there were open buffers for it, clients will be notified via `file/event` and editor will be stopped 5) only then the client is notified about a successful restore operation This PR addresses one of the two problems reported in https://www.pivotaltracker.com/story/show/184097084. # Important Notes We need to make sure that IDE correctly responds to `text/didChange` notifications.
2023-01-05 17:00:00 +03:00
[4020]: https://github.com/enso-org/enso/pull/4020
Make ArrayOverBuffer behave like an Array/Array.sort no longer mutates the Array (#4022) Most of the problems with accessing `ArrayOverBuffer` have been resolved by using `CoerceArrayNode` (https://github.com/enso-org/enso/pull/3817). In `Array.sort` we still however specialized on Array which wasn't compatible with `ArrayOverBuffer`. Similarly sorting JS or Python arrays wouldn't work. Added a specialization to `Array.sort` to deal with that case. A generic specialization (with `hasArrayElements`) not only handles `ArrayOverBuffer` but also polyglot arrays coming from JS or Python. We could have an additional specialization for `ArrayOverBuffer` only (removed in the last commit) that returns `ArrayOverBuffer` rather than `Array` although that adds additional complexity which so far is unnecessary. Also fixed an example in `Array.enso` by providing a default argument.
2023-01-09 20:49:49 +03:00
[4022]: https://github.com/enso-org/enso/pull/4022
Removing Unsafe.set_atom_field (#4023) Introducing `Meta.atom_with_hole` to create an `Atom` _with a hole_ that is then _safely_ filled in later.
2023-01-09 16:39:14 +03:00
[4023]: https://github.com/enso-org/enso/pull/4023
Report failed name resolutions in type signatures (#4030) Compiler performed name resolution of literals in type signatures but would silently fail to report any problems. This meant that wrong names or forgotten imports would sneak in to stdlib. This change introduces 2 main changes: 1) failed name resolutions are appended in `TypeNames` pass 2) `GatherDiagnostics` pass also collects and reports failures from type signatures IR Updated stdlib so that it passes given the correct gatekeepers in place.
2023-01-09 13:35:36 +03:00
[4030]: https://github.com/enso-org/enso/pull/4030
Attach visualizations to sub-expressions (#4048) Add ability to attach visualizations to sub-expressions.
2023-01-16 13:19:19 +03:00
[4048]: https://github.com/enso-org/enso/pull/4048
Create static wrappers for builtin types (#4077) https://github.com/enso-org/enso/pull/3764 introduced static wrappers for instance methods. Except it had a limitation to only be allowed for types with at least a single constructor. That excluded builtin types as well which, by default, don't have them. This limitation is problematic for Array/Vector consolidation and makes builtin types somehow second-citizens. This change lifts the limitation for builtin types only. Note that we do want to share the implementation of the generated builtin methods. At the same time due to the additional argument we have to adjust the starting index of the arguments. This change avoids messing with the existing dispatch logic, to avoid unnecessary complexity. As a result it is now possible to call builtin types' instance methods, statically: ``` arr = Array.new_1 42 Array.length arr ``` That would previously lead to missing method exception in runtime. # Important Notes The only exception is `Nothing`. Primarily because it requires `Nothing` to have a proper eigentype (`Nothing.type`) which would messed up a lot of existing logic for no obvious benefit (no more calling of `foo=Nothing` in parameters being one example).
2023-01-30 22:54:51 +03:00
[4049]: https://github.com/enso-org/enso/pull/4049
Resolve fully qualified names (#4056) Added a separate pass, `FullyQualifiedNames`, that partially resolves fully qualified names. The pass only resolves the library part of the name and replaces it with a reference to the `Main` module. There are 2 scenarios that could be potentially: 1) the code uses a fully qualified name to a component that has been parsed/compiled 2) the code uses a fully qualified name to a component that has **not** be imported For the former case, it is sufficient to just check `PackageRepository` for the presence of the library name. In the latter we have to ensure that the library has been already parsed and all its imports are resolved. That would require the reference to `Compiler` in the `FullyQualifiedNames` pass, which could then trigger a full compilation for missing library. Since it has some undesired consequences (tracking of dependencies becomes rather complex) we decided to exclude that scenario until it is really needed. # Important Notes With this change, one can use a fully qualified name directly. e.g. ``` import Standard.Base main = Standard.Base.IO.println "Hello world!" ```
2023-01-18 23:19:36 +03:00
[4056]: https://github.com/enso-org/enso/pull/4056
Report only unique warnings (#6372) This change makes sure that reported warnings are unique, based on the value of internal clock tick and ignoring differences in reassignments. Before: ![Screenshot from 2023-04-20 15-42-55](https://user-images.githubusercontent.com/292128/233415710-925c1045-37c7-49f5-9bc3-bfbfd30270a3.png) After: ![Screenshot from 2023-04-20 15-27-27](https://user-images.githubusercontent.com/292128/233415807-8cb67bc2-ac37-4db7-924e-ae7619074b5b.png) On the positive side, no further changes, like in LS, have to be done. Closes #6257.
2023-04-28 10:16:00 +03:00
[4067]: https://github.com/enso-org/enso/pull/4067
Create static wrappers for builtin types (#4077) https://github.com/enso-org/enso/pull/3764 introduced static wrappers for instance methods. Except it had a limitation to only be allowed for types with at least a single constructor. That excluded builtin types as well which, by default, don't have them. This limitation is problematic for Array/Vector consolidation and makes builtin types somehow second-citizens. This change lifts the limitation for builtin types only. Note that we do want to share the implementation of the generated builtin methods. At the same time due to the additional argument we have to adjust the starting index of the arguments. This change avoids messing with the existing dispatch logic, to avoid unnecessary complexity. As a result it is now possible to call builtin types' instance methods, statically: ``` arr = Array.new_1 42 Array.length arr ``` That would previously lead to missing method exception in runtime. # Important Notes The only exception is `Nothing`. Primarily because it requires `Nothing` to have a proper eigentype (`Nothing.type`) which would messed up a lot of existing logic for no obvious benefit (no more calling of `foo=Nothing` in parameters being one example).
2023-01-30 22:54:51 +03:00
[4077]: https://github.com/enso-org/enso/pull/4077
Custom type conversion to double from large long (#4099) When a large long would be passed to a host call expecting a double, it would crash with a ``` Cannot convert '<some long>'(language: Java, type: java.lang.Long) to Java type 'double': Invalid or lossy primitive coercion ``` That is unlikely to be expected by users. It also came up in the Statistics examples during Sum. One could workaround it by forcing the conversion manually with `.to_decimal` but it is not a permanent solution. Instead this change adds a custom type mapping from Long to Double that will do it behind the scenes with no user interaction. The mapping kicks in only for really large longs. # Important Notes Note that the _safe_ range is hardcoded in Truffle and it is not accessible in enso packages. Therefore a simple c&p for that max safe long value was necessary.
2023-01-31 18:13:00 +03:00
[4099]: https://github.com/enso-org/enso/pull/4099
Write the log in XML format suitable for VisualVM 'UI Actions' (#4110) Start `project-manager` with following options to provide first 20s of the startup sequence: ``` $ project-manager --profiling-events-log-path=start.log --profiling-path=start.npss --profiling-time=20 ``` once the `start.log` and `start.npss` files are generated (next to each other), open them in GraalVM's VisualVM: ``` $ graalvm/bin/jvisualvm --openfile start.npss ``` analyze.
2023-02-05 09:36:16 +03:00
[4110]: https://github.com/enso-org/enso/pull/4110
Report type of expressions returning polyglot values (#4111) Expressions returning polyglot values were not reporting the type of the result because we have to do additional magic that infers the correct Enso type. Since this is exactly what `TypeOfNode` does, I re-used the logic. Straightforward solution failed in tests because of assertions: ``` [enso] WARNING: Execution of function main failed (Invalid library usage. Cached library must be adopted by a RootNode before it is executed.). java.lang.AssertionError: Invalid library usage. Cached library must be adopted by a RootNode before it is executed. ``` That is why this PR replaces `ExecutionEventListener` with `ExecutionEventNodeFactory`. # Important Notes Usage of `TypeOfNode` for programs that **do not** import stdlib means that we report types that do not involve stdlib e.g. `Standard.Builtins.Main.Integer` instead of `Standard.Base.Data.Numbers.Integer`. While surprising, this is correct and I would say desirable. While reviewing the code, notice the difference in expectations in our runtime tests.
2023-02-09 04:06:27 +03:00
[4111]: https://github.com/enso-org/enso/pull/4111
Recover from serialization failures (#5591) An exception encountered during serialization prevents engine from continuing because it enters an infinite loop(!). # Important Notes The aim of this PR is to make it possible for engine to recover from the serialization failures. Any failure would mean that we enter an infinite loop in deserialization which is in turn waiting for the serialization to finish (which will never happen). In this particular case FQNs are [referencing concrete modules](https://github.com/enso-org/enso/issues/5037). A separate PR will address that.
2023-02-09 11:22:28 +03:00
[5591]: https://github.com/enso-org/enso/pull/5591
sbt runEngineDistribution ...args... to build and execute the engine (#5609) Automating the assembly of the engine and its execution into a single task. If you are modifying standard libraries, engine sources or Enso tests, you can launch `sbt` and then just: ``` sbt:enso> runEngineDistribution --run test/Tests/src/Data/Maybe_Spec.enso [info] Engine package created at built-distribution/enso-engine-0.0.0-dev-linux-amd64/enso-0.0.0-dev [info] Executing built-distribution/enso-engine-...-dev/bin/enso --run test/Tests/src/Data/Maybe_Spec.enso Maybe: [5/5, 30ms] - should have a None variant [14ms] - should have a Some variant [5ms] - should provide the `maybe` function [4ms] - should provide `is_some` [2ms] - should provide `is_none` [3ms] 5 tests succeeded. 0 tests failed.unEngineDistribution 4s 0 tests skipped. ``` the [runEngineDistribution](https://github.com/enso-org/enso/blob/3a581f29eec74d54f53271bebbc0d3503c6615e7/docs/CONTRIBUTING.md#running-enso) `sbt` input task makes sure all your sources are properly compiled and only then executes your enso source. Everything ready at a single press of Enter. # Important Notes To debug in chrome dev tools, just add `--inspect`: ``` sbt:enso> runEngineDistribution --inspect --run test/Tests/src/Data/Maybe_Spec.enso E.g. in Chrome open: devtools://devtools/bundled/js_app.html?ws=127.0.0.1:9229/7JsgjXlntK8 ``` everything gets build and one can just attach the Enso debugger.
2023-02-17 00:37:12 +03:00
[5609]: https://github.com/enso-org/enso/pull/5609
Update GraalVM to 22.3.1 (#5602) Updates the engine to GraalVM 22.3.1 version, which contains fixes for: - Chrome inspector issues - https://github.com/enso-org/enso/pull/3941/commits/38eb3b5932d91fe858c9ba96b9a0543118bd2364 # Important Notes - Update to GraalVM 22.3.1 - Remove host object wrapping workaround
2023-02-14 18:51:17 +03:00
[5602]: https://github.com/enso-org/enso/pull/5602
Optimize import/export resolution (#5700) This change adds serialization and deserialization of library bindings. In order to be functional, one needs to first generate IR and serialize bindings using `--compiled <path-to-library>` command. The bindings will be stored under the library with `.bindings` suffix. Bindings are being generated during `buildEngineDistribution` task, thus not requiring any extra steps. When resolving import/exports the compiler will first try to load module's bindings from cache. If successful, it will not schedule its imports/exports for immediate compilation, as we always did, but use the bindings info to infer the dependent modules. The current change does not make any optimizations when it comes to compiling the modules, yet. It only delays the actual compilation/loading IR from cache so that it can be done in bulk. Further optimizations will come from this opportunity such as parallel loading of caches or lazily inferring only the necessary modules. Part of https://github.com/enso-org/enso/issues/5568 work.
2023-03-01 11:53:29 +03:00
[5700]: https://github.com/enso-org/enso/pull/5700
Comparators support partial ordering (#5778)
2023-03-07 07:16:38 +03:00
[5778]: https://github.com/enso-org/enso/pull/5778
Merge ordered and unordered comparators (#5845) Merge _ordered_ and _unordered_ comparators into a single one. # Important Notes Comparator is now required to have only `compare` method: ``` type Comparator comapre : T -> T -> (Ordering|Nothing) hash : T -> Integer ```
2023-03-11 08:43:22 +03:00
[5845]: https://github.com/enso-org/enso/pull/5845
Downgrade hashing to SHA-1 and other optimizations (#5791) This change downgrades hashing algorithm used in caching IR and library bindings to SHA-1. It is sufficient and significantly faster for the purpose of simple checksum we use it for. Additionally, don't calculate the digest for serialized bytes - if we get the expected object type then we are confident about the integrity. Don't initialize Jackson's ObjectMapper for every metadata serialization/de-serialization. Initialization is very costly. Avoid unnecessary conversions between Scala and Java. Those back-and-forth `asScala` and `asJava` are pretty expensive. Finally fix an SBT warning when generating library cache. Closes https://github.com/enso-org/enso/issues/5763 # Important Notes The change cuts roughly 0.8-1s from the overall startup. This change will certainly lead to invalidation of existing caches. It is advised to simply start with a clean slate.
2023-03-09 10:36:59 +03:00
[5791]: https://github.com/enso-org/enso/pull/5791
Don't log installed engines and runtimes in prod (#5900) The `logAvailableComponentsForDebugging` will check and install all necessary components of GraalVM for every mentioned version. While not harmful, it adds up to startup time. Additionally added an option in language server startup to skip installation of GraalVM components. The latter is already performed by project-manager when opening the project and it is unnecessary to do it twice. Due to LS' architecture this configuration has to be passed around via multiple configs. Finally, skipped the attempt to install Python component on Windows - this is not supported by GraalVM atm. Closes #5749. # Important Notes The impact of this problem could be really felt the more versions of Enso and GraalVM one had since it would go through all of them.
2023-03-16 13:36:55 +03:00
[5900]: https://github.com/enso-org/enso/pull/5900
Detect conflicts between exported types and FQNs (#5986) Exporting types named the same as the module where they are defined in `Main` modules of library components may lead to accidental name conflicts. This became apparent when trying to access `Problem_Behavior` module via a fully qualified name and the compiler rejected it. This is due to the fact that `Main` module exported `Error` type defined in `Standard.Base.Error` module, thus making it impossible to access any other submodules of `Standard.Base.Error` via a fully qualified name. This change adds a warning to FullyQualifiedNames pass that detects any such future problems. While only `Error` module was affected, it was widely used in the stdlib, hence the number of changes. Closes #5902. # Important Notes I left out the potential conflict in micro-distribution, thus ensuring we actually detect and report the warning.
2023-03-22 00:09:41 +03:00
[5966]: https://github.com/enso-org/enso/pull/5966
Report only unique warnings (#6372) This change makes sure that reported warnings are unique, based on the value of internal clock tick and ignoring differences in reassignments. Before: ![Screenshot from 2023-04-20 15-42-55](https://user-images.githubusercontent.com/292128/233415710-925c1045-37c7-49f5-9bc3-bfbfd30270a3.png) After: ![Screenshot from 2023-04-20 15-27-27](https://user-images.githubusercontent.com/292128/233415807-8cb67bc2-ac37-4db7-924e-ae7619074b5b.png) On the positive side, no further changes, like in LS, have to be done. Closes #6257.
2023-04-28 10:16:00 +03:00
[5998]: https://github.com/enso-org/enso/pull/5998
Ensure new and wrapper nodes inherit UUID (#6067) Instrumentation of calls involving warning values never really worked because: 1) newly created nodes didn't set the UUID of their children 2) the instrumentable wrappers always had an empty (i.e. null) UUID and they never referred `get`/`setId` calls to their delegates On the surface, everything worked fine. Except when one actually relied on the instrumentation of values with warnings for proper setup. Then no instrumentation (replacement of nodes) was performed due to empty UUID (as required by `hasTag` of `FunctionCallInstrumentationNode`). Closes #6045. Discovered in #5893.
2023-03-27 20:49:20 +03:00
[6067]: https://github.com/enso-org/enso/pull/6067
Suspended atom fields are evaluated only once (#6151) Implements #6134. # Important Notes One can define lazy atom fields as: ```haskell type Lazy Value ~x ~y ``` the evaluation of the `x` and `y` fields is then delayed until they are needed. The evaluation happens once. Then the computed value is kept in the atom for further use.
2023-04-06 02:46:08 +03:00
[6151]: https://github.com/enso-org/enso/pull/6151
Replace IOContexts with execution env and contexts (#6171) As per design, IOContexts controlled via type signatures are going away. They are replaced by explicit `Context.if_enabled` runtime checks that will be added to particular method implementations. `production`/`development` `IOPermissions` are replaced with `live` and `design` execution enviornment. Currently, the `live` env has a hardcoded list of allowed contexts i.e. `Input` and `Output`. # Important Notes As per design PR-55. Closes #6129. Closes #6131.
2023-04-06 18:47:40 +03:00
[6171]: https://github.com/enso-org/enso/pull/6171
Removing need for asynchronous thread to execute ResourceManager finalizers (#6335) While Enso runs single-threaded, its `ResourceManager` required additional asynchronous thread to execute its _"finalizers"_. What has been necessary back then is no longer needed since _GraalVM 21.1_. GraalVM now provides support for submitting `ThreadLocalAction` that gets then picked and executed via `TruffleSafepoint` locations. This PR uses such mechanism to _"inject"_ finalizer execution into already running Enso evaluation thread. Requiring more than one thread has complicated Enso's co-existence with other Truffle language. For example Graal.js is strictly singlethreaded and used to refuse (simple) co-existence with Enso. By allowing Enso to perform all its actions in a single thread, the synergy with Graal.js becomes better.
2023-04-20 14:33:45 +03:00
[6335]: https://github.com/enso-org/enso/pull/6335
Report only unique warnings (#6372) This change makes sure that reported warnings are unique, based on the value of internal clock tick and ignoring differences in reassignments. Before: ![Screenshot from 2023-04-20 15-42-55](https://user-images.githubusercontent.com/292128/233415710-925c1045-37c7-49f5-9bc3-bfbfd30270a3.png) After: ![Screenshot from 2023-04-20 15-27-27](https://user-images.githubusercontent.com/292128/233415807-8cb67bc2-ac37-4db7-924e-ae7619074b5b.png) On the positive side, no further changes, like in LS, have to be done. Closes #6257.
2023-04-28 10:16:00 +03:00
[6372]: https://github.com/enso-org/enso/pull/6372
Reimplement `enso_project` as a proper builtin (#6352) Remove the magical code generation of `enso_project` method from codegen phase and reimplement it as a proper builtin method. The old behavior of `enso_project` was special, and violated the language semantics (regarding the `self` argument): - It was implicitly declared in every module, so it could be called without a self argument. - It can be called with explicit module as self argument, e.g. `Base.enso_project`, or `Visualizations.enso_project`. Let's avoid implicit methods on modules and let's be explicit. Let's reimplement the `enso_project` as a builtin method. To comply with the language semantics, we will have to change the signature a bit: - `enso_project` is a static method in the `Standard.Base.Meta.Enso_Project` module. - It takes an optional `project` argument (instead of taking it as an explicit self argument). Having the `enso_project` defined as a (shadowed) builtin method, we will automatically have suggestions created for it. # Important Notes - Truffle nodes are no longer generated in codegen phase for the `enso_project` method. It is a standard builtin now. - The minimal import to use `enso_project` is now `from Standard.Base.Meta.Enso_Project import enso_project`. - Tested implicitly by `org.enso.compiler.ExecCompilerTest#testInvalidEnsoProjectRef`.
2023-05-02 19:40:58 +03:00
[6352]: https://github.com/enso-org/enso/pull/6352
Limit the number of reported warnings (#6577) Artifically limiting the number of reported warnings to 100. Also added benchmarks with random Ints to investigate perf issues when dealing with warnings (future task). Ideally we would have a custom set-like collection that allows us internally to specify a maximal number of elements. But `EnsoHashMap` (and potentially `EnsoSet`) are still WIP when it comes to being PE-friendly. The change also allows for checking if the limit for the number of reported warnings has been reached. It will visualize by adding an additional "Warnings limit reached." to the visualization. The limit is configurable via `--warnings-limit` parameter to `run`. Closes #6283.
2023-05-10 14:48:31 +03:00
[6577]: https://github.com/enso-org/enso/pull/6577
Update GraalVM to 22.3.1 JDK17 (#6750) Upgrade GraalVM to 22.3.2 based on JDK17. --------- Co-authored-by: somebody1234 <ehern.lee@gmail.com>
2023-05-24 11:39:08 +03:00
[6750]: https://github.com/enso-org/enso/pull/6750
Only send suggestions updates when type changes (#6755) The change adds an additional field to `ExpressionUpdates` messages sent by `ProgramExecutionSupport` to indicate if the type of value (or its method pointer) has changed and therefore would potentially require a suggestions' update. Prior to #3729 that check was done during the instrumentation. However we still want to continue to support "pending expression" functionality therefore `SuggestionsHandler` will use the additional information to filter only the required expression updates. Most of the changes are related to adapting our tests to the new field. Closes #6706. # Important Notes The associated project now loads and navigates smoothly. Also attaching a screenshot from the project that illustrates that pending functionality continues to work: [Kazam_screencast_00006.webm](https://github.com/enso-org/enso/assets/292128/35918841-f84f-4e1c-b1b0-40e45d97e111)
2023-05-18 19:44:38 +03:00
[6755]: https://github.com/enso-org/enso/pull/6755
Add project creation time to project metadata (#6780) close #6686 Changelog: - add: `created` field to the project metadata response - update: project manager tests
2023-05-22 16:40:10 +03:00
[6780]: https://github.com/enso-org/enso/pull/6780
Runtime check of ascribed types (#6790)
2023-05-30 12:07:26 +03:00
[6790]: https://github.com/enso-org/enso/pull/6790
Add compiler pass that discovers ambiguous imports (#6868) Add a new compiler pass that analyses duplicated and ambiguous symbols from imports
2023-06-14 13:18:57 +03:00
[6868]: https://github.com/enso-org/enso/pull/6868
Improve compiler's diagnostic messages (#6931) Improve and colorize compiler's messages. Heavily inspired by `gcc`.
2023-06-08 18:43:18 +03:00
[6931]: https://github.com/enso-org/enso/pull/6931
Eliminate race condition for edit/close/open cmds (#6998) There was an inherent race condition between edit, close & open commands which could not be prevented solely using locks. `EditFileCmd` triggered `EnsureCompiledJob` which was applying edits collected over time. At the same `CloseFileCmd` and `OpenFileCmd` were executed asynchronously and required locks on compilation unit and file lock. Additionally, open file was resetting the module's runtime source irrespective of any edits that could already have been applied with the asynchronous execution in `EnsureCompiledJob`. This was visible especially during early manipulation of the project when open/close was performed due to a bug in IDE (#6843). Now commands can be run either synchronously or asynchronously. Only that way can we ensure that `close` & `open` commands finish by the time any editions are being applied to module's sources. Closes #6841. # Important Notes In the given video, `"foo"` would be greyed out because it would never be part of the module's (runtime) sources. Therefore no IR would be generated for it or instrumentation, meaning it would be present in `expressionUpdates` information necessary for IDE. [Kazam_screencast_00014.webm](https://github.com/enso-org/enso/assets/292128/226a17b8-729a-415a-803f-003a9695b2f1)
2023-06-09 15:12:46 +03:00
[6998]: https://github.com/enso-org/enso/pull/6998
Scala 2.13.11 and libraries update (#7010) Update Scala and libraries.
2023-06-14 16:15:57 +03:00
[7010]: https://github.com/enso-org/enso/pull/7010
Improvements that significantly reduce the chances of request timeouts (#7042) Request Timeouts started plaguing IDE due to numerous `executionContext/***Visualization` requests. While caused by a bug they revealed a bigger problem in the Language Server when serving large amounts of requests: 1) Long and short lived jobs are fighting for various locks. Lock contention leads to some jobs waiting for a longer than desired leading to unexpected request timeouts. Increasing timeout value is just delaying the problem. 2) Requests coming from IDE are served almost instantly and handled by various commands. Commands can issue further jobs that serve request. We apparently have and always had a single-thread thread pool for serving such jobs, leading to immediate thread starvation. Both reasons increase the chances of Request Timeouts when dealing with a large number of requests. For 2) I noticed that while we used to set the `enso-runtime-server.jobParallelism` option descriptor key to some machine-dependent value (most likely > 1), the value set would **only** be available for instrumentation. `JobExecutionEngine` where it is actually used would always get the default, i.e. a single-threaded ThreadPool. This means that this option descriptor was simply misused since its introduction. Moved that option to runtime options so that it can be set and retrieved during normal operation. Adding parallelism intensified problem 1), because now we could execute multiple jobs and they would compete for resources. It also revealed a scenario for a yet another deadlock scenario, due to invalid order of lock acquisition. See `ExecuteJob` vs `UpsertVisualisationJob` order for details. Still, a number of requests would continue to randomly timeout due to lock contention. It became apparent that `Attach/Modify/Detach-VisualisationCmd` should not wait until a triggered `UpsertVisualisationJob` sends a response to the client; long and short lived jobs will always compete for resources and we cannot guarantee that they will not timeout that way. That is why the response is sent immediately from the command handler and not from the job executed after it. This brings another problematic scenario: 1. `AttachVisualisationCmd` is executed, response sent to the client, `UpsertVisualisationJob` scheduled. 2. In the meantime `ModifyVisualisationCmd` comes and fails; command cannot find the visualization that will only be added by `UpsertVisualisationJob`, which might have not yet been scheduled to run. Remedied that by checking visualisation-related jobs that are still in progress. It also allowed for cancelling jobs which results wouldn't be used anyway (`ModifyVisualisationCmd` sends its own `UpsertVisualisationJob`). This is not a theoretical scenario, it happened frequently on IDE startup. This change does not fully solve the rather problematic setup of numerous locks, which are requested by short and long lived jobs. A better design should still be investigated. But it significantly reduces the chances of Request Timeouts which IDE had to deal with. With this change I haven't been able to experience Request Timeouts for relatively modest projects anymore. I added the possibility of logging wait times for locks to better investigate further problems. Closes #7005
2023-06-16 20:57:16 +03:00
[7042]: https://github.com/enso-org/enso/pull/7042
Implement conversions (#180312665) (#3227) * Implement conversions start wip branch for conversion methods for collaborating with marcin add conversions to MethodDispatchLibrary (wip) start MethodDispatchLibrary implementations conversions for atoms and functions Implement a bunch of missing conversion lookups final bug fixes for merged methoddispatchlibrary implementations UnresolvedConversion.resolveFor progress on invokeConversion start extracting constructors (still not working) fix a bug add some initial conversion tests fix a bug in qualified name resolution, test conversions accross modules implement error reporting, discover a ton of ignored errors... start fixing errors that we exposed in the standard library fix remaining standard lib type errors not caused by the inability to parse type signatures for operators TODO: fix type signatures for operators. all of them are broken fix type signature parsing for operators test cases for meta & polyglot play nice with polyglot start pretending unresolved conversions are unresolved symbols treat UnresolvedConversons as UnresolvedSymbols in enso user land * update RELEASES.md * disable test error about from conversions being tail calls. (pivotal issue #181113110) * add changelog entry * fix OverloadsResolutionTest * fix MethodDefinitionsTest * fix DataflowAnalysisTest * the field name for a from conversion must be 'that'. Fix remaining tests that aren't ExpressionUpdates vs. ExecutionUpdate behavioral changes * fix ModuleThisToHereTest * feat: suppress compilation errors from Builtins * Revert "feat: suppress compilation errors from Builtins" This reverts commit 63d069bd4f059baad76b7b421c4a1330ea5ffea5. * fix tests * fix: formatting Co-authored-by: Dmitry Bushev <bushevdv@gmail.com> Co-authored-by: Marcin Kostrzewa <marckostrzewa@gmail.com>
2022-02-06 12:02:09 +03:00
Prepare for release 2.0.0-alpha.18. Original commit: https://github.com/enso-org/ide/commit/cb893fdeef2568ef08b6d22c35de2dab23b6e8a5
2021-10-13 00:51:15 +03:00
# Enso 2.0.0-alpha.18 (2021-10-12)
Prepare for next development cycle. Original commit: https://github.com/enso-org/ide/commit/197b022459bcc2638292ae81c89fc76e5bc889b7
2021-09-27 23:44:55 +03:00
Bump engine to 0.2.31. Original commit: https://github.com/enso-org/ide/commit/47fc255fa1cfd1949e7c966afa420fc986f47bc9
2021-10-13 00:50:48 +03:00
<br/>![New Features](/docs/assets/tags/new_features.svg)
#### Enso Compiler
- [Updated Enso engine to version 0.2.30][engine-0.2.31]. If you're interested
in the enhancements and fixes made to the Enso compiler, you can find their
Post-merge fixes (#3130) Add GUI codeowners. Require jobs from GUI CI as part of PR. Keep prettier under control.
2021-11-01 22:44:15 +03:00
release notes
[here](https://github.com/enso-org/enso/blob/develop/RELEASES.md).
Bump engine to 0.2.31. Original commit: https://github.com/enso-org/ide/commit/47fc255fa1cfd1949e7c966afa420fc986f47bc9
2021-10-13 00:50:48 +03:00
Fix freezing after inactivity (https://github.com/enso-org/ide/pull/1776) Original commit: https://github.com/enso-org/ide/commit/c67538b57658438de6e30bdb504118ead78485a4
2021-09-30 00:13:13 +03:00
<br/>![Bug Fixes](/docs/assets/tags/bug_fixes.svg)
#### Visual Environment
- [Fixed freezing after inactivity.][1776] When the IDE window was minimized or
covered by other windows or invisible for any other reason for a duration
around one minute or longer then it would often be frozen for some seconds on
return. Now it is possible to interact with the IDE instantly, no matter how
long it had been inactive.
<br/>
[1776]: https://github.com/enso-org/ide/pull/1776
Prepare for release 2.0.0-alpha.17. Original commit: https://github.com/enso-org/ide/commit/e9344d0f461ac3bcd8217a5ebca4830a6c08533b
2021-09-24 01:24:05 +03:00
# Enso 2.0.0-alpha.17 (2021-09-23)
Update for next development cycle. Original commit: https://github.com/enso-org/ide/commit/f0ca38713d1520a2536e042e4bf8bf03c920373f
2021-09-17 20:22:34 +03:00
Delayed Visualization Attaching (https://github.com/enso-org/ide/pull/1825) Original commit: https://github.com/enso-org/ide/commit/3985f1efab6359ff3286c5728d6fa39f04cb39ef
2021-09-24 01:18:12 +03:00
<br/>![Bug Fixes](/docs/assets/tags/bug_fixes.svg)
#### Visual Environment
Fix parsing of boolean command line options (https://github.com/enso-org/ide/pull/1815) Original commit: https://github.com/enso-org/ide/commit/275eea189a72c36955f054e61d23773213c5933d
2021-09-24 01:47:05 +03:00
- [Correct handling of command-line flags.][1815] Command line arguments of the
form `--backend=false` or `--backend false` are now handled as expected and
turn off the "backend" option. The same fix has been applied to all other
boolean command-line options as well.
Delayed Visualization Attaching (https://github.com/enso-org/ide/pull/1825) Original commit: https://github.com/enso-org/ide/commit/3985f1efab6359ff3286c5728d6fa39f04cb39ef
2021-09-24 01:18:12 +03:00
- [Visualizations will be attached after project is ready.][1825] This addresses
a rare issue when initially opened visualizations were automatically closed
rather than filled with data.
Fix parsing of boolean command line options (https://github.com/enso-org/ide/pull/1815) Original commit: https://github.com/enso-org/ide/commit/275eea189a72c36955f054e61d23773213c5933d
2021-09-24 01:47:05 +03:00
<br/>
[1815]: https://github.com/enso-org/ide/pull/1815
Delayed Visualization Attaching (https://github.com/enso-org/ide/pull/1825) Original commit: https://github.com/enso-org/ide/commit/3985f1efab6359ff3286c5728d6fa39f04cb39ef
2021-09-24 01:18:12 +03:00
[1825]: https://github.com/enso-org/ide/pull/1825
Bump engine version to 0.2.30. Original commit: https://github.com/enso-org/ide/commit/62604019fea0b55665186da1f30a5ced00e67195
2021-09-24 01:22:29 +03:00
<br/>![New Features](/docs/assets/tags/new_features.svg)
#### Enso Compiler
- [Updated Enso engine to version 0.2.30][engine-0.2.30]. If you're interested
in the enhancements and fixes made to the Enso compiler, you can find their
Post-merge fixes (#3130) Add GUI codeowners. Require jobs from GUI CI as part of PR. Keep prettier under control.
2021-11-01 22:44:15 +03:00
release notes
[here](https://github.com/enso-org/enso/blob/develop/RELEASES.md).
Bump engine version to 0.2.30. Original commit: https://github.com/enso-org/ide/commit/62604019fea0b55665186da1f30a5ced00e67195
2021-09-24 01:22:29 +03:00
various default branch switch - related updates
2021-11-01 03:37:30 +03:00
[engine-0.2.30]: https://github.com/enso-org/enso/blob/develop/RELEASES.md
Bump engine version to 0.2.30. Original commit: https://github.com/enso-org/ide/commit/62604019fea0b55665186da1f30a5ced00e67195
2021-09-24 01:22:29 +03:00
Prepare for release 2.0.0-alpha.16. Original commit: https://github.com/enso-org/ide/commit/9396b96d6a42333ea6d4abbc851ba133fede11d1
2021-09-16 20:26:54 +03:00
# Enso 2.0.0-alpha.16 (2021-09-16)
Prepare for next development cycle. Original commit: https://github.com/enso-org/ide/commit/2a40c02002bd425fbdbbea2c0d82599882f5ac43
2021-09-13 02:29:53 +03:00
Auto-layout when creating nodes (https://github.com/enso-org/ide/pull/1755) Original commit: https://github.com/enso-org/ide/commit/6e5f7ef3016eea238fbdb9fe2efbcb38851feedd
2021-09-16 20:15:07 +03:00
<br/>![New Features](/docs/assets/tags/new_features.svg)
#### Visual Environment
- [Auto-layout for new nodes.][1755] When a node is selected and a new node gets
created below using <kbd>Tab</kbd> then the new node is automatically
positioned far enough to the right to find sufficient space and avoid
overlapping with existing nodes.
[1755]: https://github.com/enso-org/ide/pull/1755
Bump engine to 0.2.29. Original commit: https://github.com/enso-org/ide/commit/ed8e5ea71827528f0448fa9fa433c6650e0906df
2021-09-16 20:26:03 +03:00
#### Enso Compiler
- [Updated Enso engine to version 0.2.29][engine-0.2.29]. If you're interested
in the enhancements and fixes made to the Enso compiler, you can find their
Post-merge fixes (#3130) Add GUI codeowners. Require jobs from GUI CI as part of PR. Keep prettier under control.
2021-11-01 22:44:15 +03:00
release notes
[here](https://github.com/enso-org/enso/blob/develop/RELEASES.md).
Bump engine to 0.2.29. Original commit: https://github.com/enso-org/ide/commit/ed8e5ea71827528f0448fa9fa433c6650e0906df
2021-09-16 20:26:03 +03:00
various default branch switch - related updates
2021-11-01 03:37:30 +03:00
[engine-0.2.29]: https://github.com/enso-org/enso/blob/develop/RELEASES.md
Bump engine to 0.2.29. Original commit: https://github.com/enso-org/ide/commit/ed8e5ea71827528f0448fa9fa433c6650e0906df
2021-09-16 20:26:03 +03:00
Avoid rounding errors in canvas resolution (https://github.com/enso-org/ide/pull/1820) Original commit: https://github.com/enso-org/ide/commit/e64a6ab3a29ef9dc83fa619ffd8ba98a2766ae66
2021-09-16 20:17:44 +03:00
<br/>![Bug Fixes](/docs/assets/tags/bug_fixes.svg)
#### Visual Environment
- [Sharp rendering on screens with fractional pixel ratios.][1820]
[1820]: https://github.com/enso-org/ide/pull/1820
<br/>
Prepare for release 2.0.0-alpha.15. Original commit: https://github.com/enso-org/ide/commit/d34ef4bc9b6df521a07d3b879645bd21e166abe7
2021-09-10 01:26:50 +03:00
# Enso 2.0.0-alpha.15 (2021-09-09)
Fix parsing of the {no-}data-gathering option (https://github.com/enso-org/ide/pull/1831) Original commit: https://github.com/enso-org/ide/commit/9c29c04ec666eccbc6c69da002b746594715ce93
2021-09-08 14:02:59 +03:00
<br/>![Bug Fixes](/docs/assets/tags/bug_fixes.svg)
#### Visual Environment
- [Fixed parsing of the `--no-data-gathering` command line option.][1831] Flag's
name has been changed to `--data-gathering`, so now `--data-gathering=false`
and `--data-gathering=true` are supported as well.
[1831]: https://github.com/enso-org/ide/pull/1831
Prepare for release. Original commit: https://github.com/enso-org/ide/commit/c7c383dba604d48f6bf0bc9b5783a717571ca2cb
2021-09-03 00:47:23 +03:00
# Enso 2.0.0-alpha.14 (2021-09-02)
Update for next development cycle. Original commit: https://github.com/enso-org/ide/commit/55658708d69203144d6e8ed4fc38c214c07efd91
2021-08-27 16:51:21 +03:00
Feature flag for visualization preview (https://github.com/enso-org/ide/pull/1817) Original commit: https://github.com/enso-org/ide/commit/14e35b60f40ed3b73dca1d346fa57ae60331280f
2021-08-31 12:12:22 +03:00
<br/>![New Features](/docs/assets/tags/new_features.svg)
#### Visual Environment
- [Visualization previews are disabled.][1817] Previously, hovering over a
node's output port for more than four seconds would temporarily reveal the
Delayed Visualization Attaching (https://github.com/enso-org/ide/pull/1825) Original commit: https://github.com/enso-org/ide/commit/3985f1efab6359ff3286c5728d6fa39f04cb39ef
2021-09-24 01:18:12 +03:00
node's visualization. This behavior is disabled now.
Feature flag for visualization preview (https://github.com/enso-org/ide/pull/1817) Original commit: https://github.com/enso-org/ide/commit/14e35b60f40ed3b73dca1d346fa57ae60331280f
2021-08-31 12:12:22 +03:00
[1817]: https://github.com/enso-org/ide/pull/1817
Bump engine to 0.2.28. (https://github.com/enso-org/ide/pull/1829) Original commit: https://github.com/enso-org/ide/commit/864e3f94971861e54af9d30214cdad7aa92d28b6
2021-09-03 00:45:04 +03:00
#### Enso Compiler
- [Updated Enso engine to version 0.2.28][1829]. If you're interested in the
enhancements and fixes made to the Enso compiler, you can find their release
various default branch switch - related updates
2021-11-01 03:37:30 +03:00
notes [here](https://github.com/enso-org/enso/blob/develop/RELEASES.md).
Bump engine to 0.2.28. (https://github.com/enso-org/ide/pull/1829) Original commit: https://github.com/enso-org/ide/commit/864e3f94971861e54af9d30214cdad7aa92d28b6
2021-09-03 00:45:04 +03:00
[1829]: https://github.com/enso-org/ide/pull/1829
Prepare for release 2.0.0-alpha.13. Original commit: https://github.com/enso-org/ide/commit/301c4b044a0ad0295419ff1345f6b67e6bd6669b
2021-08-27 11:38:58 +03:00
# Enso 2.0.0-alpha.13 (2021-08-27)
Prepare for next development cycle. Original commit: https://github.com/enso-org/ide/commit/053ccbcbc1a0bc3fe6597d1ec5051b28d9168b3a
2021-08-23 12:48:38 +03:00
Bump engine to 0.2.27. (https://github.com/enso-org/ide/pull/1811) Original commit: https://github.com/enso-org/ide/commit/27ef2fc4f6326d2ad7c733b4970275b705339106
2021-08-27 11:36:04 +03:00
<br/>![New Features](/docs/assets/tags/new_features.svg)
#### Enso Compiler
- [Updated Enso engine to version 0.2.27][1811]. If you're interested in the
enhancements and fixes made to the Enso compiler, you can find their release
various default branch switch - related updates
2021-11-01 03:37:30 +03:00
notes [here](https://github.com/enso-org/enso/blob/develop/RELEASES.md).
Bump engine to 0.2.27. (https://github.com/enso-org/ide/pull/1811) Original commit: https://github.com/enso-org/ide/commit/27ef2fc4f6326d2ad7c733b4970275b705339106
2021-08-27 11:36:04 +03:00
[1811]: https://github.com/enso-org/ide/pull/1811
Prepare for release 2.0.0-alpha.12. Original commit: https://github.com/enso-org/ide/commit/20e28fa240cce04d8ae96e8a08ac00ae4a257643
2021-08-14 00:12:45 +03:00
# Enso 2.0.0-alpha.12 (2021-08-13)
Update changelog for next development cycle. Original commit: https://github.com/enso-org/ide/commit/2743e24afc273c2477a02a5739c737bb8af42691
2021-08-09 16:38:41 +03:00
Bump engine to 0.2.24. (https://github.com/enso-org/ide/pull/1798) Original commit: https://github.com/enso-org/ide/commit/12f1a4ca34adac3dc855af396b4e649b9396e92e
2021-08-14 00:11:27 +03:00
<br/>![New Features](/docs/assets/tags/new_features.svg)
Feature flag for visualization preview (https://github.com/enso-org/ide/pull/1817) Original commit: https://github.com/enso-org/ide/commit/14e35b60f40ed3b73dca1d346fa57ae60331280f
2021-08-31 12:12:22 +03:00
#### Visual Environment
Bump engine to 0.2.24. (https://github.com/enso-org/ide/pull/1798) Original commit: https://github.com/enso-org/ide/commit/12f1a4ca34adac3dc855af396b4e649b9396e92e
2021-08-14 00:11:27 +03:00
Visualization Fixes (https://github.com/enso-org/ide/pull/1804) Original commit: https://github.com/enso-org/ide/commit/838788a48f51e8a1b5c15f763427663c35c27dbc
2021-08-20 10:37:52 +03:00
- [Improvements to visualization handling][1804]. These improvements are fixing
possible performance issues around attaching and detaching visualizations.
GeoMap: Ignore points with null coordinate values (https://github.com/enso-org/ide/pull/1775) Original commit: https://github.com/enso-org/ide/commit/525b340ed28720145ac5cdb3b43e399588bf52c9
2021-08-19 13:13:01 +03:00
- [GeoMap visualization will ignore points with `null` coordinates][1775]. Now
the presence of such points in the dataset will not break initial map
positioning.
Prepare for release. Original commit: https://github.com/enso-org/ide/commit/4a4d61bdb857da9a68ea45711502841406f4ab7f
2021-08-20 11:42:47 +03:00
#### Enso Compiler
- [Updated Enso engine to version 0.2.26][1801]. If you're interested in the
Bump engine to 0.2.24. (https://github.com/enso-org/ide/pull/1798) Original commit: https://github.com/enso-org/ide/commit/12f1a4ca34adac3dc855af396b4e649b9396e92e
2021-08-14 00:11:27 +03:00
enhancements and fixes made to the Enso compiler, you can find their release
various default branch switch - related updates
2021-11-01 03:37:30 +03:00
notes [here](https://github.com/enso-org/enso/blob/develop/RELEASES.md).
Bump engine to 0.2.24. (https://github.com/enso-org/ide/pull/1798) Original commit: https://github.com/enso-org/ide/commit/12f1a4ca34adac3dc855af396b4e649b9396e92e
2021-08-14 00:11:27 +03:00
Prepare for release. Original commit: https://github.com/enso-org/ide/commit/4a4d61bdb857da9a68ea45711502841406f4ab7f
2021-08-20 11:42:47 +03:00
[1801]: https://github.com/enso-org/ide/pull/1801
GeoMap: Ignore points with null coordinate values (https://github.com/enso-org/ide/pull/1775) Original commit: https://github.com/enso-org/ide/commit/525b340ed28720145ac5cdb3b43e399588bf52c9
2021-08-19 13:13:01 +03:00
[1775]: https://github.com/enso-org/ide/pull/1775
Bump engine to 0.2.24. (https://github.com/enso-org/ide/pull/1798) Original commit: https://github.com/enso-org/ide/commit/12f1a4ca34adac3dc855af396b4e649b9396e92e
2021-08-14 00:11:27 +03:00
[1798]: https://github.com/enso-org/ide/pull/1798
Visualization Fixes (https://github.com/enso-org/ide/pull/1804) Original commit: https://github.com/enso-org/ide/commit/838788a48f51e8a1b5c15f763427663c35c27dbc
2021-08-20 10:37:52 +03:00
[1804]: https://github.com/enso-org/ide/pull/1804
Bump engine to 0.2.24. (https://github.com/enso-org/ide/pull/1798) Original commit: https://github.com/enso-org/ide/commit/12f1a4ca34adac3dc855af396b4e649b9396e92e
2021-08-14 00:11:27 +03:00
Fix changelog heading for release. Original commit: https://github.com/enso-org/ide/commit/93ca108a98e5138bd4319959f6997e51500aa044
2021-08-09 16:37:31 +03:00
# Enso 2.0.0-alpha.11 (2021-08-09)
Bump CHANGELOG.md for next release cycle. Original commit: https://github.com/enso-org/ide/commit/6b0a385adb9e65975329e6f05173cc1cf5305a1d
2021-07-23 16:43:58 +03:00
File Open Dialog (https://github.com/enso-org/ide/pull/1700) Original commit: https://github.com/enso-org/ide/commit/6f8b9a9afca59403a272dfae04ad3249566d6af7
2021-07-23 19:04:21 +03:00
This update contains major performance improvements and exposes new privacy user
settings. We will work towards stabilizing it in the next weeks in order to make
these updates be shipped in a stable release before the end of the year.
<br/>![New Features](/docs/assets/tags/new_features.svg)
#### Visual Environment
Bump changelog for release. Original commit: https://github.com/enso-org/ide/commit/c3e977e9c427cd9e4bb42b70a3f390184fe75e59
2021-08-06 20:24:41 +03:00
- [New look of open project dialog][1700]. Now it has a "Open project" title at
File Open Dialog (https://github.com/enso-org/ide/pull/1700) Original commit: https://github.com/enso-org/ide/commit/6f8b9a9afca59403a272dfae04ad3249566d6af7
2021-07-23 19:04:21 +03:00
the top.
Bump changelog for release. Original commit: https://github.com/enso-org/ide/commit/c3e977e9c427cd9e4bb42b70a3f390184fe75e59
2021-08-06 20:24:41 +03:00
- [Documentation coments are displayed next to the nodes.][1744].
File Open Dialog (https://github.com/enso-org/ide/pull/1700) Original commit: https://github.com/enso-org/ide/commit/6f8b9a9afca59403a272dfae04ad3249566d6af7
2021-07-23 19:04:21 +03:00
Bump engine to 0.2.16 (https://github.com/enso-org/ide/pull/1726) Original commit: https://github.com/enso-org/ide/commit/a2d2471e702c4c14055123f866d07603d7de1d39
2021-07-27 17:31:33 +03:00
#### Enso Compiler
Update changelog for next dev cycle. Original commit: https://github.com/enso-org/ide/commit/6541f278d1686f39744f0355a091baf28d0fe6fb
2021-08-09 16:35:05 +03:00
- [Updated Enso engine to version 0.2.22][1762]. If you are interested in the
Bump engine to 0.2.16 (https://github.com/enso-org/ide/pull/1726) Original commit: https://github.com/enso-org/ide/commit/a2d2471e702c4c14055123f866d07603d7de1d39
2021-07-27 17:31:33 +03:00
enhancements and fixes made to the Enso compiler, you can find out more
details in
various default branch switch - related updates
2021-11-01 03:37:30 +03:00
[the engine release notes](https://github.com/enso-org/enso/blob/develop/RELEASES.md).
Bump engine to 0.2.16 (https://github.com/enso-org/ide/pull/1726) Original commit: https://github.com/enso-org/ide/commit/a2d2471e702c4c14055123f866d07603d7de1d39
2021-07-27 17:31:33 +03:00
Fix expression changing during editing (https://github.com/enso-org/ide/pull/1743) Original commit: https://github.com/enso-org/ide/commit/8decddd922f17465ec8e7452a42ed5758900fc31
2021-07-30 15:38:43 +03:00
<br/>![Bug Fixes](/docs/assets/tags/bug_fixes.svg)
#### Visual Environment
Fix freezing after inactivity (https://github.com/enso-org/ide/pull/1776) Original commit: https://github.com/enso-org/ide/commit/c67538b57658438de6e30bdb504118ead78485a4
2021-09-30 00:13:13 +03:00
- [Fixed a bug where edited node expression was sometimes altered.][1743] When
Fix expression changing during editing (https://github.com/enso-org/ide/pull/1743) Original commit: https://github.com/enso-org/ide/commit/8decddd922f17465ec8e7452a42ed5758900fc31
2021-07-30 15:38:43 +03:00
editing node expression, the changes were occasionally reverted, or the
Fix freezing after inactivity (https://github.com/enso-org/ide/pull/1776) Original commit: https://github.com/enso-org/ide/commit/c67538b57658438de6e30bdb504118ead78485a4
2021-09-30 00:13:13 +03:00
grayed-out parameter names were added to the actual expression. <br/>
File Open Dialog (https://github.com/enso-org/ide/pull/1700) Original commit: https://github.com/enso-org/ide/commit/6f8b9a9afca59403a272dfae04ad3249566d6af7
2021-07-23 19:04:21 +03:00
[1700]: https://github.com/enso-org/ide/pull/1700
Project Templates (https://github.com/enso-org/ide/pull/1742) Original commit: https://github.com/enso-org/ide/commit/3452fadee9ca07edd526cd33b50a42e9a97753fc
2021-08-06 19:56:53 +03:00
[1742]: https://github.com/enso-org/ide/pull/1742
Bump engine version to 0.2.21 (https://github.com/enso-org/ide/pull/1762) Original commit: https://github.com/enso-org/ide/commit/312a5ee3728ba93559bbfb18bc9ca636725b09cb
2021-08-05 22:40:25 +03:00
[1726]: https://github.com/enso-org/ide/pull/1762
Fix expression changing during editing (https://github.com/enso-org/ide/pull/1743) Original commit: https://github.com/enso-org/ide/commit/8decddd922f17465ec8e7452a42ed5758900fc31
2021-07-30 15:38:43 +03:00
[1743]: https://github.com/enso-org/ide/pull/1743
Fix performance issues in nodes' comments (https://github.com/enso-org/ide/pull/1758) Original commit: https://github.com/enso-org/ide/commit/672a2f69a6366e482d77ba26ccf71c17d3f2dffe
2021-08-05 17:28:26 +03:00
[1744]: https://github.com/enso-org/ide/pull/1744
File Open Dialog (https://github.com/enso-org/ide/pull/1700) Original commit: https://github.com/enso-org/ide/commit/6f8b9a9afca59403a272dfae04ad3249566d6af7
2021-07-23 19:04:21 +03:00
Bump changelog for release 2.0.0-alpha.10. Original commit: https://github.com/enso-org/ide/commit/0c87b06ca0d9e487201ac9fab3dce2120f9be54f
2021-07-23 10:17:30 +03:00
# Enso 2.0.0-alpha.10 (2021-07-23)
Bump changelog. Original commit: https://github.com/enso-org/ide/commit/9624ae6019720b47ba042dbea39aecc706c5bd86
2021-07-09 12:41:58 +03:00
File Open Dialog (https://github.com/enso-org/ide/pull/1700) Original commit: https://github.com/enso-org/ide/commit/6f8b9a9afca59403a272dfae04ad3249566d6af7
2021-07-23 19:04:21 +03:00
<br/>![New Features](/docs/assets/tags/new_features.svg)
Engine 0.2.15 (https://github.com/enso-org/ide/pull/1710) Original commit: https://github.com/enso-org/ide/commit/3031f4a6869e96b9f70e44a1c6e00c57f466f9c5
2021-07-21 10:57:08 +03:00
#### Enso Compiler
- [Updated Enso engine to version 0.2.15][1710]. If you're interested in the
enhancements and fixes made to the Enso compiler, you can find out more
details in
various default branch switch - related updates
2021-11-01 03:37:30 +03:00
[the engine release notes](https://github.com/enso-org/enso/blob/develop/RELEASES.md).
Engine 0.2.15 (https://github.com/enso-org/ide/pull/1710) Original commit: https://github.com/enso-org/ide/commit/3031f4a6869e96b9f70e44a1c6e00c57f466f9c5
2021-07-21 10:57:08 +03:00
File Open Dialog (https://github.com/enso-org/ide/pull/1700) Original commit: https://github.com/enso-org/ide/commit/6f8b9a9afca59403a272dfae04ad3249566d6af7
2021-07-23 19:04:21 +03:00
<br/>
Engine 0.2.15 (https://github.com/enso-org/ide/pull/1710) Original commit: https://github.com/enso-org/ide/commit/3031f4a6869e96b9f70e44a1c6e00c57f466f9c5
2021-07-21 10:57:08 +03:00
[1710]: https://github.com/enso-org/ide/pull/1710
Bump changelog after 2.0.0-alpha.9 release. Original commit: https://github.com/enso-org/ide/commit/89dca68b741d9d04690bdb14f39a1a0aa056c07c
2021-07-20 16:20:38 +03:00
# Enso 2.0.0-alpha.9 (2021-07-16)
Undo Redo — Part 2 (https://github.com/enso-org/ide/pull/1688) Original commit: https://github.com/enso-org/ide/commit/9bc5caddc954003a9ec24ec6ee4def0b631a9f1c
2021-07-16 11:36:15 +03:00
<br/>![New Features](/docs/assets/tags/new_features.svg)
#### Visual Environment
Bump changelog after 2.0.0-alpha.9 release. Original commit: https://github.com/enso-org/ide/commit/89dca68b741d9d04690bdb14f39a1a0aa056c07c
2021-07-20 16:20:38 +03:00
- [Improved undo-redo][1653]. Node selection, enabling/disabling visualisations
and entering a node are now affected by undo/redo and are restored on project
startup.
Undo Redo — Part 2 (https://github.com/enso-org/ide/pull/1688) Original commit: https://github.com/enso-org/ide/commit/9bc5caddc954003a9ec24ec6ee4def0b631a9f1c
2021-07-16 11:36:15 +03:00
<br/>
Project Templates (https://github.com/enso-org/ide/pull/1742) Original commit: https://github.com/enso-org/ide/commit/3452fadee9ca07edd526cd33b50a42e9a97753fc
2021-08-06 19:56:53 +03:00
File Open Dialog (https://github.com/enso-org/ide/pull/1700) Original commit: https://github.com/enso-org/ide/commit/6f8b9a9afca59403a272dfae04ad3249566d6af7
2021-07-23 19:04:21 +03:00
[1640]: https://github.com/enso-org/ide/pull/1653
# Enso 2.0.0-alpha.8 (2021-06-09)
Bump changelog. Original commit: https://github.com/enso-org/ide/commit/9624ae6019720b47ba042dbea39aecc706c5bd86
2021-07-09 12:41:58 +03:00
<br/>![New Features](/docs/assets/tags/new_features.svg)
#### Enso Compiler
- [Updated Enso engine to version 0.2.12][1640]. If you're interested in the
enhancements and fixes made to the Enso compiler, you can find out more
details in
various default branch switch - related updates
2021-11-01 03:37:30 +03:00
[the engine release notes](https://github.com/enso-org/enso/blob/develop/RELEASES.md).
Bump changelog. Original commit: https://github.com/enso-org/ide/commit/9624ae6019720b47ba042dbea39aecc706c5bd86
2021-07-09 12:41:58 +03:00
Undo Redo — Part 2 (https://github.com/enso-org/ide/pull/1688) Original commit: https://github.com/enso-org/ide/commit/9bc5caddc954003a9ec24ec6ee4def0b631a9f1c
2021-07-16 11:36:15 +03:00
[1640]: https://github.com/enso-org/ide/pull/1640
Bump changelog. Original commit: https://github.com/enso-org/ide/commit/9624ae6019720b47ba042dbea39aecc706c5bd86
2021-07-09 12:41:58 +03:00
<br/>
chore: Update changelog. Original commit: https://github.com/enso-org/ide/commit/d6e211833b35cdcb8243eb8551700a614ebec9de
2021-07-06 10:50:16 +03:00
# Enso 2.0.0-alpha.7 (2021-06-06)
User Authentication in IDE (https://github.com/enso-org/ide/pull/1653) Add authentication and minimum supported version check Original commit: https://github.com/enso-org/ide/commit/2e2a804b1f5999ceafbcf7b31c417ff5f45085b1
2021-07-06 13:00:38 +03:00
<br/>![New Features](/docs/assets/tags/new_features.svg)
chore: Update changelog. Original commit: https://github.com/enso-org/ide/commit/d6e211833b35cdcb8243eb8551700a614ebec9de
2021-07-06 10:50:16 +03:00
#### Visual Environment
User Authentication in IDE (https://github.com/enso-org/ide/pull/1653) Add authentication and minimum supported version check Original commit: https://github.com/enso-org/ide/commit/2e2a804b1f5999ceafbcf7b31c417ff5f45085b1
2021-07-06 13:00:38 +03:00
- [User Authentication][1653]. Users can sign in to Enso using Google, GitHub or
email accounts.
chore: Update changelog. Original commit: https://github.com/enso-org/ide/commit/d6e211833b35cdcb8243eb8551700a614ebec9de
2021-07-06 10:50:16 +03:00
<br/>![Bug Fixes](/docs/assets/tags/bug_fixes.svg)
User Authentication in IDE (https://github.com/enso-org/ide/pull/1653) Add authentication and minimum supported version check Original commit: https://github.com/enso-org/ide/commit/2e2a804b1f5999ceafbcf7b31c417ff5f45085b1
2021-07-06 13:00:38 +03:00
#### Visual Environment
chore: Update changelog. Original commit: https://github.com/enso-org/ide/commit/d6e211833b35cdcb8243eb8551700a614ebec9de
2021-07-06 10:50:16 +03:00
- [Fix node selection bug ][1664]. Fix nodes not being deselected correctly in
some circumstances. This would lead to nodes moving too fast when dragged
[1650] or the internal state of the project being inconsistent [1626].
User Authentication in IDE (https://github.com/enso-org/ide/pull/1653) Add authentication and minimum supported version check Original commit: https://github.com/enso-org/ide/commit/2e2a804b1f5999ceafbcf7b31c417ff5f45085b1
2021-07-06 13:00:38 +03:00
[1653]: https://github.com/enso-org/ide/pull/1653
[1664]: https://github.com/enso-org/ide/pull/1664
<br/>
New release in changelog Original commit: https://github.com/enso-org/ide/commit/b4a082331b55f58d1e3fa5336cf79775abf22553
2021-06-25 18:04:37 +03:00
# Enso 2.0.0-alpha.6 (2021-06-28)
Add Next Release Entry Original commit: https://github.com/enso-org/ide/commit/0901c65d2d15f22466121aece5d99acda24d4ea5
2021-05-24 18:17:55 +03:00
<br/>![New Features](/docs/assets/tags/new_features.svg)
#### Visual Environment
Undo Redo — Part 2 (https://github.com/enso-org/ide/pull/1688) Original commit: https://github.com/enso-org/ide/commit/9bc5caddc954003a9ec24ec6ee4def0b631a9f1c
2021-07-16 11:36:15 +03:00
- [Profling mode.][1546] The IDE contains a profiling mode now which can be
Add profiling mode to GUI (https://github.com/enso-org/ide/pull/1546) Original commit: https://github.com/enso-org/ide/commit/199abd88f824f39971ff8c7872772fb7670ffda4
2021-06-10 14:24:04 +03:00
entered through a button in the top-right corner or through the keybinding
<kbd>ctrl</kbd>+<kbd>p</kbd>. This mode does not display any information yet.
In the future, it will display the running times of nodes and maybe more
useful statistics.
Implement area selection. (https://github.com/enso-org/ide/pull/1588) Original commit: https://github.com/enso-org/ide/commit/db31134558fd65ff219b597910411c01c8691603
2021-06-13 22:52:39 +03:00
- [Area selection][1588]. You can now select multiple nodes at once. Just click
and drag on the background of your graph and see the beauty of the area
selection appear.
Opening Projects in IDE (https://github.com/enso-org/ide/pull/1587) Original commit: https://github.com/enso-org/ide/commit/8f2172732a52b6acffafd2b5a0c3f710718509b1
2021-06-01 12:55:15 +03:00
- [Opening projects in application graphical interface][1587]. Press `cmd`+`o`
to bring the list of projects. Select a project on the list to open it.
Undo Redo — Part 1 (https://github.com/enso-org/ide/pull/1602) Missing parts are: * proper Text Editor support; * proper handling of deleting nodes; * undoing some UI actions (like node selection, active visualization, switching view to a different graph). Original commit: https://github.com/enso-org/ide/commit/28ad0422d57631a1b53babdf6a755949f50403a0
2021-06-11 07:34:03 +03:00
- [Initial support for undo-redo][1602]. Press <kbd>cmd</kbd>+<kbd>z</kbd> to
undo last action and <kbd>cmd</kbd>+<kbd>z</kbd> to redo last undone action.
This version of undo redo does not have proper support for text editor and
undoing UI changes (like selecting nodes).
Opening Projects in IDE (https://github.com/enso-org/ide/pull/1587) Original commit: https://github.com/enso-org/ide/commit/8f2172732a52b6acffafd2b5a0c3f710718509b1
2021-06-01 12:55:15 +03:00
Add Next Release Entry Original commit: https://github.com/enso-org/ide/commit/0901c65d2d15f22466121aece5d99acda24d4ea5
2021-05-24 18:17:55 +03:00
#### EnsoGL (rendering engine)
<br/>![Bug Fixes](/docs/assets/tags/bug_fixes.svg)
#### Visual Environment
Searcher Fixes (https://github.com/enso-org/ide/pull/1577) Original commit: https://github.com/enso-org/ide/commit/de6e14500ffccc249ef56f5ea2fbd6a762fc0aa1
2021-05-26 16:28:22 +03:00
- [Nodes in graph no longer overlap panels][1577]. The Searcher, project name,
breadcrumbs and status bar are displayed "above" nodes.
Add Next Release Entry Original commit: https://github.com/enso-org/ide/commit/0901c65d2d15f22466121aece5d99acda24d4ea5
2021-05-24 18:17:55 +03:00
#### Enso Compiler
Implement area selection. (https://github.com/enso-org/ide/pull/1588) Original commit: https://github.com/enso-org/ide/commit/db31134558fd65ff219b597910411c01c8691603
2021-06-13 22:52:39 +03:00
[1588]: https://github.com/enso-org/ide/pull/1588
Searcher Fixes (https://github.com/enso-org/ide/pull/1577) Original commit: https://github.com/enso-org/ide/commit/de6e14500ffccc249ef56f5ea2fbd6a762fc0aa1
2021-05-26 16:28:22 +03:00
[1577]: https://github.com/enso-org/ide/pull/1577
Opening Projects in IDE (https://github.com/enso-org/ide/pull/1587) Original commit: https://github.com/enso-org/ide/commit/8f2172732a52b6acffafd2b5a0c3f710718509b1
2021-06-01 12:55:15 +03:00
[1587]: https://github.com/enso-org/ide/pull/1587
Undo Redo — Part 1 (https://github.com/enso-org/ide/pull/1602) Missing parts are: * proper Text Editor support; * proper handling of deleting nodes; * undoing some UI actions (like node selection, active visualization, switching view to a different graph). Original commit: https://github.com/enso-org/ide/commit/28ad0422d57631a1b53babdf6a755949f50403a0
2021-06-11 07:34:03 +03:00
[1602]: https://github.com/enso-org/ide/pull/1602
Emit correct events when deselecting all nodes. (https://github.com/enso-org/ide/pull/1664) Original commit: https://github.com/enso-org/ide/commit/63ff1fe4319d24300e9882abfac25b05d422197a
2021-07-06 10:42:08 +03:00
[1602]: https://github.com/enso-org/ide/pull/1664
[1602]: https://github.com/enso-org/ide/pull/1650
[1602]: https://github.com/enso-org/ide/pull/1626
Searcher Fixes (https://github.com/enso-org/ide/pull/1577) Original commit: https://github.com/enso-org/ide/commit/de6e14500ffccc249ef56f5ea2fbd6a762fc0aa1
2021-05-26 16:28:22 +03:00
Add last entries to alpha 5 Original commit: https://github.com/enso-org/ide/commit/ab3e04db5529bc913e57410063cb56a8e26d4c42
2021-05-24 17:56:58 +03:00
# Enso 2.0.0-alpha.5 (2021-05-14)
Close and Fullscreen buttons for IDE in the cloud (https://github.com/enso-org/ide/pull/1511) Original commit: https://github.com/enso-org/ide/commit/71c3b39110f6d53f742af8aff3f41f2f943beffe
2021-04-26 16:06:52 +03:00
<br/>![New Features](/docs/assets/tags/new_features.svg)
#### Visual Environment
Create new project action in searcher. (https://github.com/enso-org/ide/pull/1566) Original commit: https://github.com/enso-org/ide/commit/5adc95289dc6359fc56146bd9796f74009426029
2021-05-21 16:24:17 +03:00
- [Create New Project action in Searcher][1566]. When you bring the searcher
with tab having no node selected, a new action will be available next to the
examples and code suggestions: `Create New Project`. When you choose it by
clicking with mouse or selecting and pressing enter, a new unnamed project
will be created and opened in the application. Then you can give a name to
this project.
Enable build signing for macOS and Windows binaries. (https://github.com/enso-org/ide/pull/1366) Original commit: https://github.com/enso-org/ide/commit/0c339d8b590407aaf3aadad724dbe1673145ccfd
2021-06-10 12:56:51 +03:00
- [Signed builds.][1366] Our builds are signed and will avoid warnings from the
operating system about being untrusted.
Create new project action in searcher. (https://github.com/enso-org/ide/pull/1566) Original commit: https://github.com/enso-org/ide/commit/5adc95289dc6359fc56146bd9796f74009426029
2021-05-21 16:24:17 +03:00
#### EnsoGL (rendering engine)
Implement number and range pickers. (https://github.com/enso-org/ide/pull/1524) Original commit: https://github.com/enso-org/ide/commit/b361fdb5296f8e4f247bfa174ac11a89404fe68d
2021-05-21 12:41:03 +03:00
- [Components for picking numbers and ranges.][1524]. We now have some internal
re-usable UI components for selecting numbers or a range. Stay tuned for them
appearing in the IDE.
Update changelog for release of Enso 2.0.0-alpha.4. Original commit: https://github.com/enso-org/ide/commit/fc9454a2d66a749bb2c0eff494210f1157b55b54
2021-05-04 13:54:13 +03:00
<br/>![Bug Fixes](/docs/assets/tags/bug_fixes.svg)
#### Visual Environment
Fix changelog entry Original commit: https://github.com/enso-org/ide/commit/46574683044ceb5e660728e1ef09ed4fb9bfa362
2021-06-04 14:05:00 +03:00
- [Delete key will delete selected nodes][1538]. Only the non-intuitive
backspace key was assigned to this action before.
Deselect visualization when its node gets removed (https://github.com/enso-org/ide/pull/1556) Original commit: https://github.com/enso-org/ide/commit/f9778d60d2e34ab7b975885e1224c5b8b3b2edc3
2021-05-13 10:50:01 +03:00
- [It is possible to move around after deleting a node with a selected
visualization][1556]. Deleting a node while its attached visualization was
selected made it impossible to pan or zoom around the stage afterwards. This
error is fixed now.
Correctly handle case when wasm streaming is failing. (https://github.com/enso-org/ide/pull/1561) Original commit: https://github.com/enso-org/ide/commit/72349b8371ec511cb3708b991cc1a73928da00b5
2021-05-11 12:33:20 +03:00
- [Fixed an internal error that would make the IDE fail on some browser.][1561].
Instead of crashing on browser that don't support the feature we use, we are
now just start a little bit slower.
Delete key shall delete nodes. (https://github.com/enso-org/ide/pull/1538) Original commit: https://github.com/enso-org/ide/commit/70ce429e8b8af5db72bba737355d470ff83b167e
2021-05-07 12:27:20 +03:00
Create new project action in searcher. (https://github.com/enso-org/ide/pull/1566) Original commit: https://github.com/enso-org/ide/commit/5adc95289dc6359fc56146bd9796f74009426029
2021-05-21 16:24:17 +03:00
#### Enso Compiler
Bump engine version to 0.2.11 (https://github.com/enso-org/ide/pull/1541) Original commit: https://github.com/enso-org/ide/commit/86fc4a010fcbb440575515aaa779f45876867909
2021-05-10 18:39:31 +03:00
- [Updated Enso engine to version 0.2.11][1541].
Update changelog for release of Enso 2.0.0-alpha.4. Original commit: https://github.com/enso-org/ide/commit/fc9454a2d66a749bb2c0eff494210f1157b55b54
2021-05-04 13:54:13 +03:00
If you're interested in the enhancements and fixes made to the Enso compiler,
you can find their release notes
various default branch switch - related updates
2021-11-01 03:37:30 +03:00
[here](https://github.com/enso-org/enso/blob/develop/RELEASES.md).
Update changelog for release of Enso 2.0.0-alpha.4. Original commit: https://github.com/enso-org/ide/commit/fc9454a2d66a749bb2c0eff494210f1157b55b54
2021-05-04 13:54:13 +03:00
Enable build signing for macOS and Windows binaries. (https://github.com/enso-org/ide/pull/1366) Original commit: https://github.com/enso-org/ide/commit/0c339d8b590407aaf3aadad724dbe1673145ccfd
2021-06-10 12:56:51 +03:00
[1366]: https://github.com/enso-org/ide/pull/1366
Create new project action in searcher. (https://github.com/enso-org/ide/pull/1566) Original commit: https://github.com/enso-org/ide/commit/5adc95289dc6359fc56146bd9796f74009426029
2021-05-21 16:24:17 +03:00
[1541]: https://github.com/enso-org/ide/pull/1541
Delete key shall delete nodes. (https://github.com/enso-org/ide/pull/1538) Original commit: https://github.com/enso-org/ide/commit/70ce429e8b8af5db72bba737355d470ff83b167e
2021-05-07 12:27:20 +03:00
[1538]: https://github.com/enso-org/ide/pull/1538
Add last entries to alpha 5 Original commit: https://github.com/enso-org/ide/commit/ab3e04db5529bc913e57410063cb56a8e26d4c42
2021-05-24 17:56:58 +03:00
[1524]: https://github.com/enso-org/ide/pull/1524
[1556]: https://github.com/enso-org/ide/pull/1556
[1561]: https://github.com/enso-org/ide/pull/1561
[1566]: https://github.com/enso-org/ide/pull/1566
Delete key shall delete nodes. (https://github.com/enso-org/ide/pull/1538) Original commit: https://github.com/enso-org/ide/commit/70ce429e8b8af5db72bba737355d470ff83b167e
2021-05-07 12:27:20 +03:00
Update changelog for release of Enso 2.0.0-alpha.4. Original commit: https://github.com/enso-org/ide/commit/fc9454a2d66a749bb2c0eff494210f1157b55b54
2021-05-04 13:54:13 +03:00
<br/>
# Enso 2.0.0-alpha.4 (2021-05-04)
<br/>![New Features](/docs/assets/tags/new_features.svg)
#### Visual Environment
Close and Fullscreen buttons for IDE in the cloud (https://github.com/enso-org/ide/pull/1511) Original commit: https://github.com/enso-org/ide/commit/71c3b39110f6d53f742af8aff3f41f2f943beffe
2021-04-26 16:06:52 +03:00
- [Window management buttons.][1511]. The IDE now has components for
Update changelog for release of Enso 2.0.0-alpha.4. Original commit: https://github.com/enso-org/ide/commit/fc9454a2d66a749bb2c0eff494210f1157b55b54
2021-05-04 13:54:13 +03:00
"fullscreen" and "close" buttons. They will when running IDE in a cloud
environment where no native window buttons are available.
Passing options to backend and adding `--verbose` flag (https://github.com/enso-org/ide/pull/1531) ref #2938 Original commit: https://github.com/enso-org/ide/commit/a5c5762ddac95c827a72c021238b31bc06c821fd
2021-04-30 00:21:18 +03:00
- [Customizable backend options][1531]. When invoking Enso IDE through command
Update changelog for release of Enso 2.0.0-alpha.4. Original commit: https://github.com/enso-org/ide/commit/fc9454a2d66a749bb2c0eff494210f1157b55b54
2021-05-04 13:54:13 +03:00
line interface, it is possible to add the `--` argument separator. All
arguments following the separator will be passed to the backend.
Passing options to backend and adding `--verbose` flag (https://github.com/enso-org/ide/pull/1531) ref #2938 Original commit: https://github.com/enso-org/ide/commit/a5c5762ddac95c827a72c021238b31bc06c821fd
2021-04-30 00:21:18 +03:00
- [Added `--verbose` parameter][1531]. If `--verbose` is given as command line
argument, the IDE and the backend will produce more detailed logs.
Close and Fullscreen buttons for IDE in the cloud (https://github.com/enso-org/ide/pull/1511) Original commit: https://github.com/enso-org/ide/commit/71c3b39110f6d53f742af8aff3f41f2f943beffe
2021-04-26 16:06:52 +03:00
<br/>![Bug Fixes](/docs/assets/tags/bug_fixes.svg)
#### Visual Environment
Update changelog for release of Enso 2.0.0-alpha.4. Original commit: https://github.com/enso-org/ide/commit/fc9454a2d66a749bb2c0eff494210f1157b55b54
2021-05-04 13:54:13 +03:00
- [Some command line arguments were not applied correctly in the IDE][1536].
Some arguments were not passed correctly to the IDE leading to erroneous
behavior or appearance of the electron app. This is now fixed.
Close and Fullscreen buttons for IDE in the cloud (https://github.com/enso-org/ide/pull/1511) Original commit: https://github.com/enso-org/ide/commit/71c3b39110f6d53f742af8aff3f41f2f943beffe
2021-04-26 16:06:52 +03:00
#### Enso Compiler
If you're interested in the enhancements and fixes made to the Enso compiler,
you can find their release notes
various default branch switch - related updates
2021-11-01 03:37:30 +03:00
[here](https://github.com/enso-org/enso/blob/develop/RELEASES.md).
Close and Fullscreen buttons for IDE in the cloud (https://github.com/enso-org/ide/pull/1511) Original commit: https://github.com/enso-org/ide/commit/71c3b39110f6d53f742af8aff3f41f2f943beffe
2021-04-26 16:06:52 +03:00
[1511]: https://github.com/enso-org/ide/pull/1511
Update changelog for release of Enso 2.0.0-alpha.4. Original commit: https://github.com/enso-org/ide/commit/fc9454a2d66a749bb2c0eff494210f1157b55b54
2021-05-04 13:54:13 +03:00
[1536]: https://github.com/enso-org/ide/pull/1536
Passing options to backend and adding `--verbose` flag (https://github.com/enso-org/ide/pull/1531) ref #2938 Original commit: https://github.com/enso-org/ide/commit/a5c5762ddac95c827a72c021238b31bc06c821fd
2021-04-30 00:21:18 +03:00
[1531]: https://github.com/enso-org/ide/pull/1531
Close and Fullscreen buttons for IDE in the cloud (https://github.com/enso-org/ide/pull/1511) Original commit: https://github.com/enso-org/ide/commit/71c3b39110f6d53f742af8aff3f41f2f943beffe
2021-04-26 16:06:52 +03:00
<br/>
Set new release Original commit: https://github.com/enso-org/ide/commit/59482b1c115732ea22f9594089667cb2e2f53435
2021-04-13 18:27:25 +03:00
# Enso 2.0.0-alpha.3 (2020-04-13)
Don't insert imports when method calls are created through searcher (https://github.com/enso-org/ide/pull/1209) Original commit: https://github.com/enso-org/ide/commit/fef2e4f7b0eaca0365a048b3e27c848a39f89fb5
2021-03-08 15:03:00 +03:00
<br/>![New Learning Resources](/docs/assets/tags/new_learning_resources.svg)
<br/>![New Features](/docs/assets/tags/new_features.svg)
#### Visual Environment
Point users to the Enso repo (https://github.com/enso-org/ide/pull/1470) Original commit: https://github.com/enso-org/ide/commit/5b1b6e6185474d5e591bfdfff4ac699a4d4cf4e1
2021-04-13 17:41:26 +03:00
- [The status bar reports connectivity issues][1316]. The IDE maintains a
connection to the Enso Language Server. If this connection is lost, any
unsaved and further work will be lost. In this build we have added a
notification in the status bar to signal that the connection has been lost and
that the IDE must be restarted. In future, the IDE will try to automatically
reconnect.
- [Visualizations can now be maximised to fill the screen][1355] by selecting
the node and pressing space twice. To quit this view, press space again.
- [Visualizations are previewed when you hover over an output port.][1363] There
is now a quick preview for visualizations and error descriptions. Hovering
over a node output will first show a tooltip with the type information and
then, after some time, will show the visualization of the node. This preview
visualization will be located above other nodes, whereas the normal view, will
be shown below nodes. Errors will show the preview visualization immediately.
Nodes without type information will also show the visualization immediately.
You can enter a quick preview mode by pressing ctrl (or command on macOS),
which will show the preview visualization immediately when hovering above a
node's output port.
Database Visualizations (https://github.com/enso-org/ide/pull/1335) Original commit: https://github.com/enso-org/ide/commit/132ae3e2fe3d269b1e23ef9179282978d81c2411
2021-03-25 19:03:22 +03:00
- [Database Visualizations][1335]. Visualizations for the Database library have
been added. The Table visualization now automatically executes the underlying
Point users to the Enso repo (https://github.com/enso-org/ide/pull/1470) Original commit: https://github.com/enso-org/ide/commit/5b1b6e6185474d5e591bfdfff4ac699a4d4cf4e1
2021-04-13 17:41:26 +03:00
query to display its results as a table. In addition, the SQL Query
Database Visualizations (https://github.com/enso-org/ide/pull/1335) Original commit: https://github.com/enso-org/ide/commit/132ae3e2fe3d269b1e23ef9179282978d81c2411
2021-03-25 19:03:22 +03:00
visualization allows the user to see the query that is going to be run against
the database.
Support Dataframes in Histogram and Scatter Plot Visualizations (https://github.com/enso-org/ide/pull/1377) Original commit: https://github.com/enso-org/ide/commit/cd3a6e920cf371615a718d855e091224b5d82c2f
2021-03-30 10:36:42 +03:00
- [Histogram and Scatter Plot now support Dataframes.][1377] The `Table` and
`Column` datatypes are properly visualized. Scatter Plot can display points of
Point users to the Enso repo (https://github.com/enso-org/ide/pull/1470) Original commit: https://github.com/enso-org/ide/commit/5b1b6e6185474d5e591bfdfff4ac699a4d4cf4e1
2021-04-13 17:41:26 +03:00
different colors, shapes and sizes, all as defined by the data within the
Support Dataframes in Histogram and Scatter Plot Visualizations (https://github.com/enso-org/ide/pull/1377) Original commit: https://github.com/enso-org/ide/commit/cd3a6e920cf371615a718d855e091224b5d82c2f
2021-03-30 10:36:42 +03:00
`Table`.
Visual improvements 2 (https://github.com/enso-org/ide/pull/1419) Original commit: https://github.com/enso-org/ide/commit/1fa34b0df346a14d1f961804a8c1acdeaca27591
2021-04-02 11:01:50 +03:00
- [Many small visual improvements.][1419] See the source issue for more details.
Dark theme fixes (https://github.com/enso-org/ide/pull/1444) Original commit: https://github.com/enso-org/ide/commit/9903484daa4c3764e6d4711c6232d692ceb7e564
2021-04-07 15:01:51 +03:00
- The dark theme is officially supported now. You can start the IDE with the
`--theme=dark` option to enable it.
Point users to the Enso repo (https://github.com/enso-org/ide/pull/1470) Original commit: https://github.com/enso-org/ide/commit/5b1b6e6185474d5e591bfdfff4ac699a4d4cf4e1
2021-04-13 17:41:26 +03:00
- You can hide the node labels with the `--no-node-labels` option. This is
useful when creating demo videos.
- [Added a Heatmap visualization.][1438] Just as for the Scatter Plot, it
supports visualizing `Table`, but also `Vector`.
Update breadcrumb bar design (https://github.com/enso-org/ide/pull/1471) Original commit: https://github.com/enso-org/ide/commit/0ad870bb669a9367db62731f911f43f49e5e986a
2021-04-13 16:59:41 +03:00
- [Add a background to the status bar][1447].
- [Display breadcrumbs behind nodes and other objects][1471].
Image Visualizations (https://github.com/enso-org/ide/pull/1367) Original commit: https://github.com/enso-org/ide/commit/ba97fc7572c6222c9ca05ad84baadbf5cc8f96b7
2021-04-08 12:14:13 +03:00
- [Image visualization.][1367]. Visualizations for the Enso Image library. Now
Point users to the Enso repo (https://github.com/enso-org/ide/pull/1470) Original commit: https://github.com/enso-org/ide/commit/5b1b6e6185474d5e591bfdfff4ac699a4d4cf4e1
2021-04-13 17:41:26 +03:00
you can display the `Image` type and a string with an image encoded in base64.
The histogram visualization has been adjusted, allowing you to display the
values of the precomputed bins, which is useful when the dataset is relatively
big, and it's cheaper to send the precomputed bins rather than the entire
dataset.
Show node output type right under the node, not in pop-up. (https://github.com/enso-org/ide/pull/1427) Original commit: https://github.com/enso-org/ide/commit/4bf917e0cc5994375565719c0b4e8cbbf71e7b29
2021-05-14 16:06:14 +03:00
- [Output type labels.][1427] The labels, that show the output type of a node on
hover, appear now in a fixed position right below the node, instead of a
pop-up, as they did before.
Losing LS connection will display a statusbar message. (https://github.com/enso-org/ide/pull/1316) Original commit: https://github.com/enso-org/ide/commit/01f481e5d4352dcc4eb18f9efdfd2630a42fc1c1
2021-03-12 14:56:33 +03:00
Don't insert imports when method calls are created through searcher (https://github.com/enso-org/ide/pull/1209) Original commit: https://github.com/enso-org/ide/commit/fef2e4f7b0eaca0365a048b3e27c848a39f89fb5
2021-03-08 15:03:00 +03:00
<br/>![Bug Fixes](/docs/assets/tags/bug_fixes.svg)
#### Visual Environment
Point users to the Enso repo (https://github.com/enso-org/ide/pull/1470) Original commit: https://github.com/enso-org/ide/commit/5b1b6e6185474d5e591bfdfff4ac699a4d4cf4e1
2021-04-13 17:41:26 +03:00
- [Not adding spurious imports][1209]. Fixed cases where the IDE was adding
unnecessary library imports when selecting hints from the node searcher. This
makes the generated textual code much easier to read, and reduces the
likelihood of accidental name collisions.
- [Hovering over an output port shows a pop-up with the result type of a
node][1312]. This allows easy discovery of the result type of a node, which
can help with both debugging and development.
- [Visualizations can define the context for preprocessor evaluation][1291].
Users can now decide which module's context should be used for visualization
preprocessor. This allows providing visualizations with standard library
Allow visualizations to define context module for preprocessor (https://github.com/enso-org/ide/pull/1291) Ref #2705 Original commit: https://github.com/enso-org/ide/commit/4e7dfd0bd01351ced1348400516927b9e83657eb
2021-03-10 13:09:45 +03:00
functionalities or defining utilities that are shared between multiple
visualizations.
Point users to the Enso repo (https://github.com/enso-org/ide/pull/1470) Original commit: https://github.com/enso-org/ide/commit/5b1b6e6185474d5e591bfdfff4ac699a4d4cf4e1
2021-04-13 17:41:26 +03:00
- [Fixed an issue with multiple instances of the IDE running.][1314] This fixes
an issue where multiple instances of the IDE (or even other applications)
could lead to the IDE not working.
Do not crash the IDE when logging non-string objects. (https://github.com/enso-org/ide/pull/1313) Original commit: https://github.com/enso-org/ide/commit/ff5e927623c13a7607998d7afddf3db7093c20ce
2021-03-12 22:37:53 +03:00
- [Allow JS to log arbitrary objects.][1313] Previously using `console.log` in a
Add --no-data-gathering as a startup option (https://github.com/enso-org/ide/pull/1328) Add --no-data-gathering as a startup option This option will disable sending any data to Mixpanel. Original commit: https://github.com/enso-org/ide/commit/145153b70290e5de7556f3a6ae43f90bed5e3d28
2021-03-19 13:43:34 +03:00
visualisation or during development would crash the IDE. Now it correctly logs
Point users to the Enso repo (https://github.com/enso-org/ide/pull/1470) Original commit: https://github.com/enso-org/ide/commit/5b1b6e6185474d5e591bfdfff4ac699a4d4cf4e1
2021-04-13 17:41:26 +03:00
the string representation of the object. This is great for debugging custom
visualizations.
- [Fix the mouse cursor offset on systems with fractional display
scaling][1064]. The cursor now works with any display scaling, instead of
there being an offset between the visible cursor and the cursor selection.
Temporarily disable area selection (https://github.com/enso-org/ide/pull/1318) Original commit: https://github.com/enso-org/ide/commit/aeee0bcbf2069e3e16ae5c2e620acf8fcbf2354c
2021-03-12 15:24:33 +03:00
- [Disable area selection][1318]. The area selection was visible despite being
non-functional. To avoid confusion, area selection has been disabled until it
is [correctly implemented][479].
Point users to the Enso repo (https://github.com/enso-org/ide/pull/1470) Original commit: https://github.com/enso-org/ide/commit/5b1b6e6185474d5e591bfdfff4ac699a4d4cf4e1
2021-04-13 17:41:26 +03:00
- [Fix an error after adding a node][1332]. Sometimes, after picking a
suggestion, the inserted node was spuriously annotated with "The name could
not be found" error.
Fix pasting multiline code in single-lined text area (https://github.com/enso-org/ide/pull/1348) When pasting multiline code in a single-lined text area, only the first line will be inserted. Original commit: https://github.com/enso-org/ide/commit/a59a3b578eb6624d7eb9d21c55e560fce1f951c4
2021-03-23 17:08:18 +03:00
- [Handle syntax errors in custom-defined visualizations][1341]. The IDE is now
Point users to the Enso repo (https://github.com/enso-org/ide/pull/1470) Original commit: https://github.com/enso-org/ide/commit/5b1b6e6185474d5e591bfdfff4ac699a4d4cf4e1
2021-04-13 17:41:26 +03:00
able to run properly, even if some of the custom visualizations inside a
project contain syntax errors.
Fix pasting multiline code in single-lined text area (https://github.com/enso-org/ide/pull/1348) When pasting multiline code in a single-lined text area, only the first line will be inserted. Original commit: https://github.com/enso-org/ide/commit/a59a3b578eb6624d7eb9d21c55e560fce1f951c4
2021-03-23 17:08:18 +03:00
- [Fix issues with pasting multi-line text into single-line text fields][1348].
Point users to the Enso repo (https://github.com/enso-org/ide/pull/1470) Original commit: https://github.com/enso-org/ide/commit/5b1b6e6185474d5e591bfdfff4ac699a4d4cf4e1
2021-04-13 17:41:26 +03:00
The line in the copied text will be inserted and all additional lines will be
Fix pasting multiline code in single-lined text area (https://github.com/enso-org/ide/pull/1348) When pasting multiline code in a single-lined text area, only the first line will be inserted. Original commit: https://github.com/enso-org/ide/commit/a59a3b578eb6624d7eb9d21c55e560fce1f951c4
2021-03-23 17:08:18 +03:00
ignored.
Add --no-data-gathering as a startup option (https://github.com/enso-org/ide/pull/1328) Add --no-data-gathering as a startup option This option will disable sending any data to Mixpanel. Original commit: https://github.com/enso-org/ide/commit/145153b70290e5de7556f3a6ae43f90bed5e3d28
2021-03-19 13:43:34 +03:00
- [Users can opt out of anonymous data gathering.][1328] This can be done with
Point users to the Enso repo (https://github.com/enso-org/ide/pull/1470) Original commit: https://github.com/enso-org/ide/commit/5b1b6e6185474d5e591bfdfff4ac699a4d4cf4e1
2021-04-13 17:41:26 +03:00
the `--no-data-gathering` command-line flag when starting the IDE.
Add a theming API for visualizations (https://github.com/enso-org/ide/pull/1358) Original commit: https://github.com/enso-org/ide/commit/916d733e76fab8c1ff44159d229d3c293eeb60a2
2021-03-24 21:08:42 +03:00
- [Provide a theming API for JavaScript visualizations][1358]. It is now
possible to use the Enso theming engine while developing custom visualizations
in JavaScript. You can query it for all IDE colors, including the colors used
to represent types.
Point users to the Enso repo (https://github.com/enso-org/ide/pull/1470) Original commit: https://github.com/enso-org/ide/commit/5b1b6e6185474d5e591bfdfff4ac699a4d4cf4e1
2021-04-13 17:41:26 +03:00
- [You can now start the IDE service without a window again.][1353] The command
Show visualization on output port hover. (https://github.com/enso-org/ide/pull/1363) Original commit: https://github.com/enso-org/ide/commit/b869971f446ada972cdefae06d9136b3ebf424d1
2021-03-30 21:51:32 +03:00
line argument `--no-window` now starts all the required backend services
Point users to the Enso repo (https://github.com/enso-org/ide/pull/1470) Original commit: https://github.com/enso-org/ide/commit/5b1b6e6185474d5e591bfdfff4ac699a4d4cf4e1
2021-04-13 17:41:26 +03:00
again, and prints the port on the command line. This allows you to open the
IDE in a web browser of your choice.
- [JS visualizations have gestures consistent with the IDE][1291]. Panning and
zooming now works just as expected using both a trackpad and mouse.
Fix build failing when executing `run watch` on a clean build. (https://github.com/enso-org/ide/pull/1395) Original commit: https://github.com/enso-org/ide/commit/c4008d4699231388b8aec66fa4c159e5821fcdab
2021-03-31 17:31:46 +03:00
- [Running `watch` command works on first try.][1395]. Running the build command
`run watch` would fail if it was run as the first command on a clean
repository. This now works.
Point users to the Enso repo (https://github.com/enso-org/ide/pull/1470) Original commit: https://github.com/enso-org/ide/commit/5b1b6e6185474d5e591bfdfff4ac699a4d4cf4e1
2021-04-13 17:41:26 +03:00
- [The `inputType` field of visualizations is actually taken into
consideration][1384]. The visualization chooser shows only the entries that
work properly for the node's output type.
- [Fix applying the output of the selected node to the expression of a new
node][1385]. For example, having selected a node with `Table` output and
adding a new node with expression `at "x" == "y"`, the selected node was
applied to the right side of `==`: `at "x" == operator1."y"` instead of
`operator1.at "x" == "y"`.
- [`Enso_Project.data` is visible in the searcher][1393].
- [The Geo Map visualization recognizes columns regardless of the case of their
name][1392]. This allows visualizing tables with columns like `LONGITUDE` or
Geomap Case Insensitive (https://github.com/enso-org/ide/pull/1392) Original commit: https://github.com/enso-org/ide/commit/85a1adc862e831f679fb8f1f4b1f7e7ee6e48d8f
2021-03-26 19:42:50 +03:00
`Longitude`, where previously only `longitude` was recognized.
Point users to the Enso repo (https://github.com/enso-org/ide/pull/1470) Original commit: https://github.com/enso-org/ide/commit/5b1b6e6185474d5e591bfdfff4ac699a4d4cf4e1
2021-04-13 17:41:26 +03:00
- [It is possible now to switch themes][1390]. Additionally, the theme manager
was integrated with the FRP event engine, which has been a long-standing issue
in the IDE. Themes management was exposed to JavaScript with the
`window.theme` variable. It is even possible to change and develop themes live
by editing theme variables directly in the Chrome Inspector. Use the following
command to give this a go:
`theme.snapshot("t1"); theme.get("t1").interactiveMode()`.
Show that visualization is selected (https://github.com/enso-org/ide/pull/1412) Original commit: https://github.com/enso-org/ide/commit/e3e073326be8d1e11de4eaf75a44c7ca2e2e2057
2021-03-31 17:46:18 +03:00
- [The active visualization is highlighted.][1412] Now it is clearly visible
when the mouse events are passed to the visualization.
Point users to the Enso repo (https://github.com/enso-org/ide/pull/1470) Original commit: https://github.com/enso-org/ide/commit/5b1b6e6185474d5e591bfdfff4ac699a4d4cf4e1
2021-04-13 17:41:26 +03:00
- [Fixed an issue where projects containing certain language constructs failed
to load.][1413]
Fix Backend Dying (https://github.com/enso-org/ide/pull/1428) Original commit: https://github.com/enso-org/ide/commit/63917f4a656118129e1235f213537805be6e112e
2021-04-02 16:52:22 +03:00
- [Fixed a case where IDE could lose connection to the backend after some
time.][1428]
Point users to the Enso repo (https://github.com/enso-org/ide/pull/1470) Original commit: https://github.com/enso-org/ide/commit/5b1b6e6185474d5e591bfdfff4ac699a4d4cf4e1
2021-04-13 17:41:26 +03:00
- [Improved the performance of the graph editor, particularly when opening a
project for the first time.][1445]
Don't insert imports when method calls are created through searcher (https://github.com/enso-org/ide/pull/1209) Original commit: https://github.com/enso-org/ide/commit/fef2e4f7b0eaca0365a048b3e27c848a39f89fb5
2021-03-08 15:03:00 +03:00
#### EnsoGL (rendering engine)
Point users to the Enso repo (https://github.com/enso-org/ide/pull/1470) Original commit: https://github.com/enso-org/ide/commit/5b1b6e6185474d5e591bfdfff4ac699a4d4cf4e1
2021-04-13 17:41:26 +03:00
- [Unified shadow generation][1411]. Added a toolset to create shadows for
Visual improvements 1+2 (https://github.com/enso-org/ide/pull/1411) Original commit: https://github.com/enso-org/ide/commit/9b60a911b959401d9fbe605a113ad0f140fef04b
2021-03-30 21:09:54 +03:00
arbitrary UI components.
Run prettier on changelog Original commit: https://github.com/enso-org/ide/commit/ca6bfa99bfe8595765c18d701f9618f289e0a136
2021-03-31 10:12:43 +03:00
Don't insert imports when method calls are created through searcher (https://github.com/enso-org/ide/pull/1209) Original commit: https://github.com/enso-org/ide/commit/fef2e4f7b0eaca0365a048b3e27c848a39f89fb5
2021-03-08 15:03:00 +03:00
#### Enso Compiler
If you're interested in the enhancements and fixes made to the Enso compiler,
you can find their release notes
various default branch switch - related updates
2021-11-01 03:37:30 +03:00
[here](https://github.com/enso-org/enso/blob/develop/RELEASES.md#enso-0210-2021-04-07).
Don't insert imports when method calls are created through searcher (https://github.com/enso-org/ide/pull/1209) Original commit: https://github.com/enso-org/ide/commit/fef2e4f7b0eaca0365a048b3e27c848a39f89fb5
2021-03-08 15:03:00 +03:00
Theme management (https://github.com/enso-org/ide/pull/1390) Original commit: https://github.com/enso-org/ide/commit/c8bfe4296dc8d842473c02182ffe0d573552d132
2021-03-30 17:16:46 +03:00
[1064]: https://github.com/enso-org/ide/pull/1064
Don't insert imports when method calls are created through searcher (https://github.com/enso-org/ide/pull/1209) Original commit: https://github.com/enso-org/ide/commit/fef2e4f7b0eaca0365a048b3e27c848a39f89fb5
2021-03-08 15:03:00 +03:00
[1209]: https://github.com/enso-org/ide/pull/1209
Allow visualizations to define context module for preprocessor (https://github.com/enso-org/ide/pull/1291) Ref #2705 Original commit: https://github.com/enso-org/ide/commit/4e7dfd0bd01351ced1348400516927b9e83657eb
2021-03-10 13:09:45 +03:00
[1291]: https://github.com/enso-org/ide/pull/1291
Scatterplot and Histogram: panning, pinching and RMB zooming works as expected. (https://github.com/enso-org/ide/pull/1311) Original commit: https://github.com/enso-org/ide/commit/9c26d936f48fa1bdb339ce9ddeeaefb07ffa6e54
2021-03-25 12:54:11 +03:00
[1311]: https://github.com/enso-org/ide/pull/1311
Theme management (https://github.com/enso-org/ide/pull/1390) Original commit: https://github.com/enso-org/ide/commit/c8bfe4296dc8d842473c02182ffe0d573552d132
2021-03-30 17:16:46 +03:00
[1313]: https://github.com/enso-org/ide/pull/1313
[1314]: https://github.com/enso-org/ide/pull/1314
Losing LS connection will display a statusbar message. (https://github.com/enso-org/ide/pull/1316) Original commit: https://github.com/enso-org/ide/commit/01f481e5d4352dcc4eb18f9efdfd2630a42fc1c1
2021-03-12 14:56:33 +03:00
[1316]: https://github.com/enso-org/ide/pull/1316
Temporarily disable area selection (https://github.com/enso-org/ide/pull/1318) Original commit: https://github.com/enso-org/ide/commit/aeee0bcbf2069e3e16ae5c2e620acf8fcbf2354c
2021-03-12 15:24:33 +03:00
[1318]: https://github.com/enso-org/ide/pull/1318
Theme management (https://github.com/enso-org/ide/pull/1390) Original commit: https://github.com/enso-org/ide/commit/c8bfe4296dc8d842473c02182ffe0d573552d132
2021-03-30 17:16:46 +03:00
[1328]: https://github.com/enso-org/ide/pull/1328
Fullscreen Visualization (https://github.com/enso-org/ide/pull/1355) Original commit: https://github.com/enso-org/ide/commit/ebf5c4f052f8189e22cb6645732821d7fe250aae
2021-03-30 13:43:05 +03:00
[1355]: https://github.com/enso-org/ide/pull/1355
Engine updates after adding node: send import first, then the new node (https://github.com/enso-org/ide/pull/1332) When the user creates a node through the searcher that needs additional imports, those imports should be added before or simultaneously to the node content to avoid an invalid intermediate state. This was done in the wrong order before this commit. Original commit: https://github.com/enso-org/ide/commit/da6d66fc05ef554c9796cb0c16a58dd3923cada1
2021-03-23 19:38:00 +03:00
[1332]: https://github.com/enso-org/ide/pull/1332
[1341]: https://github.com/enso-org/ide/pull/1341
Fix pasting multiline code in single-lined text area (https://github.com/enso-org/ide/pull/1348) When pasting multiline code in a single-lined text area, only the first line will be inserted. Original commit: https://github.com/enso-org/ide/commit/a59a3b578eb6624d7eb9d21c55e560fce1f951c4
2021-03-23 17:08:18 +03:00
[1341]: https://github.com/enso-org/ide/pull/1341
[1348]: https://github.com/enso-org/ide/pull/1348
Run all backend processed even if the IDE package is run with --no-window (https://github.com/enso-org/ide/pull/1353) Original commit: https://github.com/enso-org/ide/commit/3381bb455f9a63e01674fc7704fba3ff8a8e601d
2021-03-22 13:38:05 +03:00
[1353]: https://github.com/enso-org/ide/pull/1353
Fix build failing when executing `run watch` on a clean build. (https://github.com/enso-org/ide/pull/1395) Original commit: https://github.com/enso-org/ide/commit/c4008d4699231388b8aec66fa4c159e5821fcdab
2021-03-31 17:31:46 +03:00
[1395]: https://github.com/enso-org/ide/pull/1395
Show visualization on output port hover. (https://github.com/enso-org/ide/pull/1363) Original commit: https://github.com/enso-org/ide/commit/b869971f446ada972cdefae06d9136b3ebf424d1
2021-03-30 21:51:32 +03:00
[1363]: https://github.com/enso-org/ide/pull/1363
Show visualization available for node output type only. (https://github.com/enso-org/ide/pull/1384) Original commit: https://github.com/enso-org/ide/commit/d4cc824e34dbca142eae2e3aa855d48ea10ed742
2021-03-30 15:25:38 +03:00
[1384]: https://github.com/enso-org/ide/pull/1384
Fix strange this argument applying in searcher. (https://github.com/enso-org/ide/pull/1385) Original commit: https://github.com/enso-org/ide/commit/3ace4e4b124a510cc6c1f13cb05bad721a7a850c
2021-03-26 14:00:25 +03:00
[1385]: https://github.com/enso-org/ide/pull/1385
Theme management (https://github.com/enso-org/ide/pull/1390) Original commit: https://github.com/enso-org/ide/commit/c8bfe4296dc8d842473c02182ffe0d573552d132
2021-03-30 17:16:46 +03:00
[1390]: https://github.com/enso-org/ide/pull/1390
Geomap Case Insensitive (https://github.com/enso-org/ide/pull/1392) Original commit: https://github.com/enso-org/ide/commit/85a1adc862e831f679fb8f1f4b1f7e7ee6e48d8f
2021-03-26 19:42:50 +03:00
[1392]: https://github.com/enso-org/ide/pull/1392
Theme management (https://github.com/enso-org/ide/pull/1390) Original commit: https://github.com/enso-org/ide/commit/c8bfe4296dc8d842473c02182ffe0d573552d132
2021-03-30 17:16:46 +03:00
[1393]: https://github.com/enso-org/ide/pull/1393
[479]: https://github.com/enso-org/ide/issues/479
Fullscreen Visualization (https://github.com/enso-org/ide/pull/1355) Original commit: https://github.com/enso-org/ide/commit/ebf5c4f052f8189e22cb6645732821d7fe250aae
2021-03-30 13:43:05 +03:00
[1335]: https://github.com/enso-org/ide/pull/1335
[1358]: https://github.com/enso-org/ide/pull/1358
Support Dataframes in Histogram and Scatter Plot Visualizations (https://github.com/enso-org/ide/pull/1377) Original commit: https://github.com/enso-org/ide/commit/cd3a6e920cf371615a718d855e091224b5d82c2f
2021-03-30 10:36:42 +03:00
[1377]: https://github.com/enso-org/ide/pull/1377
Visual improvements 1+2 (https://github.com/enso-org/ide/pull/1411) Original commit: https://github.com/enso-org/ide/commit/9b60a911b959401d9fbe605a113ad0f140fef04b
2021-03-30 21:09:54 +03:00
[1411]: https://github.com/enso-org/ide/pull/1411
Show that visualization is selected (https://github.com/enso-org/ide/pull/1412) Original commit: https://github.com/enso-org/ide/commit/e3e073326be8d1e11de4eaf75a44c7ca2e2e2057
2021-03-31 17:46:18 +03:00
[1412]: https://github.com/enso-org/ide/pull/1412
Visual improvements 2 (https://github.com/enso-org/ide/pull/1419) Original commit: https://github.com/enso-org/ide/commit/1fa34b0df346a14d1f961804a8c1acdeaca27591
2021-04-02 11:01:50 +03:00
[1419]: https://github.com/enso-org/ide/pull/1419
Fix Nested Macros Deserialization (https://github.com/enso-org/ide/pull/1413) Original commit: https://github.com/enso-org/ide/commit/c433eb01ddd10a7719d33d8e99f2bd47c7e71311
2021-04-01 23:56:23 +03:00
[1413]: https://github.com/enso-org/ide/pull/1413
Fix Backend Dying (https://github.com/enso-org/ide/pull/1428) Original commit: https://github.com/enso-org/ide/commit/63917f4a656118129e1235f213537805be6e112e
2021-04-02 16:52:22 +03:00
[1428]: https://github.com/enso-org/ide/pull/1428
Create prototype heatmap visualization. (https://github.com/enso-org/ide/pull/1438) Original commit: https://github.com/enso-org/ide/commit/10e08be303f3db80faf25ff96e0296f6b75ea42a
2021-04-04 18:42:38 +03:00
[1438]: https://github.com/enso-org/ide/pull/1438
Image Visualizations (https://github.com/enso-org/ide/pull/1367) Original commit: https://github.com/enso-org/ide/commit/ba97fc7572c6222c9ca05ad84baadbf5cc8f96b7
2021-04-08 12:14:13 +03:00
[1367]: https://github.com/enso-org/ide/pull/1367
Suppressing spurious type updates. (https://github.com/enso-org/ide/pull/1445) Original commit: https://github.com/enso-org/ide/commit/42e6ea046a9ccf51e6c78839a5bd8955826e4c5d
2021-04-09 18:25:24 +03:00
[1445]: https://github.com/enso-org/ide/pull/1445
Close and Fullscreen buttons for IDE in the cloud (https://github.com/enso-org/ide/pull/1511) Original commit: https://github.com/enso-org/ide/commit/71c3b39110f6d53f742af8aff3f41f2f943beffe
2021-04-26 16:06:52 +03:00
[1447]: https://github.com/enso-org/ide/pull/1447
[1471]: https://github.com/enso-org/ide/pull/1471
[1511]: https://github.com/enso-org/ide/pull/1511
Don't insert imports when method calls are created through searcher (https://github.com/enso-org/ide/pull/1209) Original commit: https://github.com/enso-org/ide/commit/fef2e4f7b0eaca0365a048b3e27c848a39f89fb5
2021-03-08 15:03:00 +03:00
<br/>
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
# Enso 2.0.0-alpha.2 (2020-03-04)
Making CI config more generic (https://github.com/enso-org/ide/pull/1158) Original commit: https://github.com/enso-org/ide/commit/66e45cd1ddbe0b831bab588a0ec2ca6d39421a2e
2021-02-02 08:07:43 +03:00
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
This is a release focused on bug-fixing, stability, and performance. It improves
the performance of workflows and visualizations, and improves the look and feel
CI Fixes (https://github.com/enso-org/ide/pull/1304) Original commit: https://github.com/enso-org/ide/commit/0ff9e3f62bc9b657e5c73e360f48b314354be5a4
2021-03-05 18:22:19 +03:00
of the graphical interface. In addition, the graphical interface now informs the
users about errors and where they originate.
Making CI config more generic (https://github.com/enso-org/ide/pull/1158) Original commit: https://github.com/enso-org/ide/commit/66e45cd1ddbe0b831bab588a0ec2ca6d39421a2e
2021-02-02 08:07:43 +03:00
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
<br/>![New Learning Resources](/docs/assets/tags/new_learning_resources.svg)
- [Learn how to define custom data visualizations in
Enso][podcast-custom-visualizations].
CI Fixes (https://github.com/enso-org/ide/pull/1304) Original commit: https://github.com/enso-org/ide/commit/0ff9e3f62bc9b657e5c73e360f48b314354be5a4
2021-03-05 18:22:19 +03:00
- [Learn how to use Java libraries in Enso, to build a
webserver][podcast-java-interop].
- [Learn how to use Javascript libraries in Enso, to build custom server-side
website rendering][podcast-http-server].
- [Discover why Enso Compiler is so fast and how it was built to support a
dual-representation language][podcast-compiler-internals].
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
- [Learn more about the vision behind Enso and about its planned
future][podcast-future-of-enso].
Making CI config more generic (https://github.com/enso-org/ide/pull/1158) Original commit: https://github.com/enso-org/ide/commit/66e45cd1ddbe0b831bab588a0ec2ca6d39421a2e
2021-02-02 08:07:43 +03:00
Add description of draggable visualisations to changelog. (https://github.com/enso-org/ide/pull/1174) Original commit: https://github.com/enso-org/ide/commit/846907b651080436bf86cf3a85025e5fac689d27
2021-02-06 00:53:42 +03:00
<br/>![New Features](/docs/assets/tags/new_features.svg)
#### Visual Environment
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
- [Errors in workflows are now displayed in the graphical interface][1215].
Previously, these errors were silently skipped, which was non-intuitive and
hard to understand. Now, the IDE displays both dataflow errors and panics in a
CI Fixes (https://github.com/enso-org/ide/pull/1304) Original commit: https://github.com/enso-org/ide/commit/0ff9e3f62bc9b657e5c73e360f48b314354be5a4
2021-03-05 18:22:19 +03:00
nice and descriptive fashion.
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
- [Added geographic map support for Tables (data frames).][1187] Tables that
CI Fixes (https://github.com/enso-org/ide/pull/1304) Original commit: https://github.com/enso-org/ide/commit/0ff9e3f62bc9b657e5c73e360f48b314354be5a4
2021-03-05 18:22:19 +03:00
have `latitude`, `longitude`, and optionally `label` columns can now be shown
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
as points on a map.
CI Fixes (https://github.com/enso-org/ide/pull/1304) Original commit: https://github.com/enso-org/ide/commit/0ff9e3f62bc9b657e5c73e360f48b314354be5a4
2021-03-05 18:22:19 +03:00
- [Added a shortcut for live reloading of visualization files.][1190] This
drastically improves how quickly new visualizations can be tested during their
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
development. This is _currently_ limited in that, after reloading
visualization definitions, the currently visible visualizations must be
CI Fixes (https://github.com/enso-org/ide/pull/1304) Original commit: https://github.com/enso-org/ide/commit/0ff9e3f62bc9b657e5c73e360f48b314354be5a4
2021-03-05 18:22:19 +03:00
switched to another and switched back to refresh their content. See the [video
podcast about building custom visualizations][podcast-custom-visualizations]
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
to learn more.
- [Added a visual indicator of the ongoing standard library compilation][1264].
CI Fixes (https://github.com/enso-org/ide/pull/1304) Original commit: https://github.com/enso-org/ide/commit/0ff9e3f62bc9b657e5c73e360f48b314354be5a4
2021-03-05 18:22:19 +03:00
Currently, each time IDE is started, the backend needs to compile the standard
library before it can provide IDE with type information and values. Because of
that, not all functionalities are ready to work directly after starting the
IDE. Now, there is a visible indication of the ongoing background process.
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
- [Added the ability to reposition visualisations.][1096] There is now an icon
in the visualization action bar that allows dragging the visualization away
from a node. Once the visualization has been moved, another icon appears that
can pin the visualization back to the node.
- [There is now an API to show Version Control System (like Git) status for
nodes][1160].
<br/>![Bug Fixes](/docs/assets/tags/bug_fixes.svg)
#### Visual Environment
- [You can now use the table visualization to display data frames][1181]. Please
note, that large tables will get truncated to 2000 entries. This limitation
will be lifted in future releases.
- [Performance improvements during visual workflow][1067]. Nodes added with the
CI Fixes (https://github.com/enso-org/ide/pull/1304) Original commit: https://github.com/enso-org/ide/commit/0ff9e3f62bc9b657e5c73e360f48b314354be5a4
2021-03-05 18:22:19 +03:00
searcher will have their values automatically assigned to newly generated
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
variables, which allows the Enso Engine to cache intermediate values and hence
improve visualization performance.
- [Minor documentation rendering fixes][1098]. Fixed cases where text would be
misinterpreted as a tag, added support for new tag types, added support for
more common characters, properly renders overflowing text.
- [Improved handling of projects created with other IDE versions][1214]. The IDE
is now better at dealing with incompatible metadata in files, which stores
node visual position information, the history of chosen searcher suggestions,
etc. This will allow IDE to correctly open projects that were created using a
CI Fixes (https://github.com/enso-org/ide/pull/1304) Original commit: https://github.com/enso-org/ide/commit/0ff9e3f62bc9b657e5c73e360f48b314354be5a4
2021-03-05 18:22:19 +03:00
different IDE version and prevent unnecessary loss of metadata.
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
- Pressing and holding up and down arrow keys make the list view selection move
continuously.
- The shortcuts to close the application and to toggle the developer tools at
runtime now work on all supported platforms.
- [The loading progress indicator remains visible while IDE initializes][1237].
Previously the loading progress indicator completed too quickly and stopped
spinning before the IDE was ready. Now it stays active, giving a visual
indication that the initialization is still in progress.
- [Fixed visual glitch where a node's text was displayed as white on a white
background][1264]. Most notably this occurred with the output node of a
function generated using the node collapse refactoring.
CI Fixes (https://github.com/enso-org/ide/pull/1304) Original commit: https://github.com/enso-org/ide/commit/0ff9e3f62bc9b657e5c73e360f48b314354be5a4
2021-03-05 18:22:19 +03:00
- Many visual glitches were fixed, including small "pixel-like" artifacts
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
appearing on the screen.
- [Several parser improvements][1274]. The parser used in the IDE has been
updated to the latest version. This resolves several issues with language
CI Fixes (https://github.com/enso-org/ide/pull/1304) Original commit: https://github.com/enso-org/ide/commit/0ff9e3f62bc9b657e5c73e360f48b314354be5a4
2021-03-05 18:22:19 +03:00
constructs like `import`, lambdas, and parentheses, whereupon typing certain
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
text the edit could be automatically reverted.
- [The auto-import functionality was improved][1279]. Libraries' `Main` modules
CI Fixes (https://github.com/enso-org/ide/pull/1304) Original commit: https://github.com/enso-org/ide/commit/0ff9e3f62bc9b657e5c73e360f48b314354be5a4
2021-03-05 18:22:19 +03:00
are omitted in expressions inserted by the searcher. For example, the `point`
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
method of `Geo` library will be displayed as `Geo.point` and will insert
import `Geo` instead of `Geo.Main`.
- Cursors in text editors behave correctly now (they are not affected by scene
pan and zoom). This was possible because of the new multi-camera management
system implemented in EnsoGL.
Filter out Unresolved_Symbol when coloring ports (https://github.com/enso-org/ide/pull/1408) Original commit: https://github.com/enso-org/ide/commit/e74b8c3fd99da86f263cf4b81d7cfa82f65151c5
2021-03-30 18:48:55 +03:00
- [Fixed method names highlighted in pink.][1408] There was a bug introduced
after one of the latest Engine updates, that sent `Unresolved_symbol` types,
which made all methods pink. This is fixed now.
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
#### EnsoGL (rendering engine)
CI Fixes (https://github.com/enso-org/ide/pull/1304) Original commit: https://github.com/enso-org/ide/commit/0ff9e3f62bc9b657e5c73e360f48b314354be5a4
2021-03-05 18:22:19 +03:00
- A new multi-camera management system, allowing the same shape systems to be
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
rendered on different layers from different cameras. The implementation
automatically caches the same shape system definitions per scene layer in
order to minimize the amount of WebGL draw calls and hence improve
performance.
- A new depth-ordering mechanism for symbols and shapes. It is now possible to
define depth order dependencies between symbols, shapes, and shape systems.
- Various performance improvements, especially for the text rendering engine.
- Display objects handle visibility correctly now. Display objects are not
visible by default and need to be attached to a visible parent to be shown on
the screen.
#### Enso Compiler
If you're interested in the enhancements and fixes made to the Enso compiler,
you can find their release notes
various default branch switch - related updates
2021-11-01 03:37:30 +03:00
[here](https://github.com/enso-org/enso/blob/develop/RELEASES.md#enso-026-2021-03-02).
Add description of draggable visualisations to changelog. (https://github.com/enso-org/ide/pull/1174) Original commit: https://github.com/enso-org/ide/commit/846907b651080436bf86cf3a85025e5fac689d27
2021-02-06 00:53:42 +03:00
Update CHANGELOG.md Original commit: https://github.com/enso-org/ide/commit/8e1da4feaffa29aac8ce9dd57d1b8c8b52eae3bd
2021-03-05 01:47:50 +03:00
[1067]: https://github.com/enso-org/ide/pull/1067
[1096]: https://github.com/enso-org/ide/pull/1096
Applies fixes for Doc Parser. (https://github.com/enso-org/ide/pull/1098) Original commit: https://github.com/enso-org/ide/commit/4f82dcff180de90d11a836a02f869b4c087ba63b
2021-02-11 19:00:22 +03:00
[1098]: https://github.com/enso-org/ide/pull/1098
Enable table visualisation for Tables. (https://github.com/enso-org/ide/pull/1181) Original commit: https://github.com/enso-org/ide/commit/b6c4339778b23e9d6fda30f479202d927925c102
2021-02-06 00:57:16 +03:00
[1181]: https://github.com/enso-org/ide/pull/1181
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
[1215]: https://github.com/enso-org/ide/pull/1215
Add API to mark node VCS status. (https://github.com/enso-org/ide/pull/1160) Original commit: https://github.com/enso-org/ide/commit/3c8b4b37adadcd25432e4b3ab5b87dc6cc83f78f
2021-02-12 15:38:06 +03:00
[1160]: https://github.com/enso-org/ide/pull/1160
A shortcut for reloading visualization files. (https://github.com/enso-org/ide/pull/1190) Original commit: https://github.com/enso-org/ide/commit/8308c1ce7ffd0a79501330806fc78d983ea876b3
2021-02-10 20:19:54 +03:00
[1190]: https://github.com/enso-org/ide/pull/1190
Update geomaps to allow dataframes as input. (https://github.com/enso-org/ide/pull/1187) Allow Tables to feed the Geo Maps visualization. Uses the columns longitude, latitude and label. Extracts the data through an Enso preprocessor. Original commit: https://github.com/enso-org/ide/commit/1ec89ee1dc4a113bf756d601dd4eeb2ff476baee
2021-02-16 13:47:57 +03:00
[1187]: https://github.com/enso-org/ide/pull/1187
missing changelog updates + fixed link (https://github.com/enso-org/ide/pull/1275) Original commit: https://github.com/enso-org/ide/commit/ea0f6c05959e9c949570f00723c0e3bbb0eb2165
2021-03-01 11:38:16 +03:00
[1068]: https://github.com/enso-org/ide/pull/1068
Prevent IDE from failing to start when metadata are invalid (https://github.com/enso-org/ide/pull/1214) Original commit: https://github.com/enso-org/ide/commit/07927e1a14bc843c91a6c63cc4067ad7bc8c00eb
2021-02-19 17:20:25 +03:00
[1214]: https://github.com/enso-org/ide/pull/1214
Progress indicator for WASM loading is capped at 30%. This keeps it active and spinning until IDE looks ready. (https://github.com/enso-org/ide/pull/1262) Original commit: https://github.com/enso-org/ide/commit/7cd367ec6b470e0ad0e2eee713bd94075061a2da
2021-02-25 17:23:55 +03:00
[1237]: https://github.com/enso-org/ide/pull/1237
missing changelog updates + fixed link (https://github.com/enso-org/ide/pull/1275) Original commit: https://github.com/enso-org/ide/commit/ea0f6c05959e9c949570f00723c0e3bbb0eb2165
2021-03-01 11:38:16 +03:00
[1264]: https://github.com/enso-org/ide/pull/1264
Engine 0.2.6 (https://github.com/enso-org/ide/pull/1286) Contains parser update by @mwu-tow Original commit: https://github.com/enso-org/ide/commit/bfd27b735fb8da0f33f9f4a3043a232693915718
2021-03-02 16:21:50 +03:00
[1274]: https://github.com/enso-org/ide/pull/1274
Fix Main modules (https://github.com/enso-org/ide/pull/1279) Original commit: https://github.com/enso-org/ide/commit/79f906db59cf61119e6a9ef302b85f5509c1fbe3
2021-03-02 14:47:13 +03:00
[1279]: https://github.com/enso-org/ide/pull/1279
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
[podcast-java-interop]:
https://www.youtube.com/watch?v=bcpOEX1x06I&t=468s&ab_channel=Enso
[podcast-compiler-internals]:
https://www.youtube.com/watch?v=BibjcUjdkO4&ab_channel=Enso
[podcast-custom-visualizations]:
https://www.youtube.com/watch?v=wFkh5LgAZTs&t=5439s&ab_channel=Enso
[podcast-http-server]:
https://www.youtube.com/watch?v=BYUAL4ksEgY&ab_channel=Enso
[podcast-future-of-enso]:
https://www.youtube.com/watch?v=rF8DuJPOfTs&t=1863s&ab_channel=Enso
Implement tooltips that show the type of an output port on hover. (https://github.com/enso-org/ide/pull/1312) Original commit: https://github.com/enso-org/ide/commit/f03a6525f7e7c9b977dac7e389bdef5c19532599
2021-03-17 12:48:11 +03:00
[1312]: https://github.com/enso-org/ide/pull/1312
Filter out Unresolved_Symbol when coloring ports (https://github.com/enso-org/ide/pull/1408) Original commit: https://github.com/enso-org/ide/commit/e74b8c3fd99da86f263cf4b81d7cfa82f65151c5
2021-03-30 18:48:55 +03:00
[1408]: https://github.com/enso-org/ide/pull/1408
Add description of draggable visualisations to changelog. (https://github.com/enso-org/ide/pull/1174) Original commit: https://github.com/enso-org/ide/commit/846907b651080436bf86cf3a85025e5fac689d27
2021-02-06 00:53:42 +03:00
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
<br/>
Fix electron shortcuts to enable toggling the developer tools and quitting the application. (https://github.com/enso-org/ide/pull/1173) Original commit: https://github.com/enso-org/ide/commit/8f2a1a23fdcb8d16659363a0edf87d92e5b43c9a
2021-02-06 00:51:41 +03:00
Making CI config more generic (https://github.com/enso-org/ide/pull/1158) Original commit: https://github.com/enso-org/ide/commit/66e45cd1ddbe0b831bab588a0ec2ca6d39421a2e
2021-02-02 08:07:43 +03:00
# Enso 2.0.0-alpha.1 (2020-01-26)
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
This is the first release of Enso, a general-purpose programming language and
environment for interactive data processing. It is a tool that spans the entire
stack, going from high-level visualization and communication to the nitty-gritty
of backend services, all in a single language.
Making CI config more generic (https://github.com/enso-org/ide/pull/1158) Original commit: https://github.com/enso-org/ide/commit/66e45cd1ddbe0b831bab588a0ec2ca6d39421a2e
2021-02-02 08:07:43 +03:00
<br/>![Release Notes](/docs/assets/tags/release_notes.svg)
#### Anonymous Data Collection
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
Please note that this release collects anonymous usage data which will be used
to improve Enso and prepare it for a stable release. We will switch to opt-in
data collection in stable version releases. The usage data will not contain your
code (expressions above nodes), however, reported errors may contain brief
snippets of out of context code that specifically leads to the error, like "the
method 'foo' does not exist on Number". The following data will be collected:
Making CI config more generic (https://github.com/enso-org/ide/pull/1158) Original commit: https://github.com/enso-org/ide/commit/66e45cd1ddbe0b831bab588a0ec2ca6d39421a2e
2021-02-02 08:07:43 +03:00
- Session length.
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
- Graph editing events (node create, dele, position change, connect, disconnect,
collapse, edit start, edit end). This will not include any information about
node expressions used.
Making CI config more generic (https://github.com/enso-org/ide/pull/1158) Original commit: https://github.com/enso-org/ide/commit/66e45cd1ddbe0b831bab588a0ec2ca6d39421a2e
2021-02-02 08:07:43 +03:00
- Navigation events (camera movement, scope change).
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
- Visualization events (visualization open, close, switch). This will not
include any information about the displayed data nor the rendered
visualization itself.
Making CI config more generic (https://github.com/enso-org/ide/pull/1158) Original commit: https://github.com/enso-org/ide/commit/66e45cd1ddbe0b831bab588a0ec2ca6d39421a2e
2021-02-02 08:07:43 +03:00
- Project management events (project open, close, rename).
Improving release notes (https://github.com/enso-org/ide/pull/1289) Original commit: https://github.com/enso-org/ide/commit/b30782222eca44e6d957cac0c0e4dde80e72c381
2021-03-04 21:01:35 +03:00
- Errors (IDE crashes, WASM panics, Project Manager errors, Language Server
errors, Compiler errors).
Making CI config more generic (https://github.com/enso-org/ide/pull/1158) Original commit: https://github.com/enso-org/ide/commit/66e45cd1ddbe0b831bab588a0ec2ca6d39421a2e
2021-02-02 08:07:43 +03:00
- Performance statistics (minimum, maximum, average GUI refresh rate).
Reference in New Issue Copy Permalink