[
https://issues.apache.org/jira/browse/FLINK-23907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Smirnov updated FLINK-23907:
---------------------------------
Description:
Hey!
We are a collaborative group of researchers from JetBrains Research and Oregon
State University, and we are testing our data-driven
[plugin|https://github.com/JetBrains-Research/data-driven-type-migration],
which is based on the IntelliJ's [Type
Migration|https://www.jetbrains.com/help/idea/type-migration.html] framework
and adjusts it using custom structural-replace templates that express the
adaptations required to perform the type changes.
I want to apply several type changes using it and open the PR, thus introducing
primitive functional interfaces in order to prevent unnecessary boxing (like
BooleanSupplier instead Supplier<Boolean>, OptionalInt instead of
Optional<Integer>, Predicate<T> instead of Function<T, Boolean>, etc. ), since
it can affect the performance of the code (Effective Java, Items 44, 61).
The patch itself is already prepared (because it is done automatically using
the plugin), so I guess I will need to open this ticket, receive your approval,
and then open the PR?
It would help us a lot to evaluate the usefulness of our approach!
Thank you in advance!
was:
Hey!
We are a group of researchers, and we are testing our data-driven
[plugin|https://github.com/JetBrains-Research/data-driven-type-migration],
which is based on the IntelliJ's [Type
Migration|https://www.jetbrains.com/help/idea/type-migration.html] framework
and adjusts it using custom structural-replace templates that express the
adaptations required to perform the type change.
I want to apply several type changes using it and open the PR, thus introducing
primitive functional interfaces in order to prevent unnecessary boxing (like
BooleanSupplier instead Supplier<Boolean>, OptionalInt instead of
Optional<Integer>, etc. ), since it can affect the performance of the code
(Effective Java, Items 44, 61).
The patch itself is already prepared, so I guess I will need to open this
ticket, receive your approval, and then open the PR?
Thank you in advance!
> Type Migration: introducing primitive functional interfaces
> -----------------------------------------------------------
>
> Key: FLINK-23907
> URL: https://issues.apache.org/jira/browse/FLINK-23907
> Project: Flink
> Issue Type: Improvement
> Reporter: Oleg Smirnov
> Priority: Minor
> Labels: refactoring, type-migration
>
> Hey!
> We are a collaborative group of researchers from JetBrains Research and
> Oregon State University, and we are testing our data-driven
> [plugin|https://github.com/JetBrains-Research/data-driven-type-migration],
> which is based on the IntelliJ's [Type
> Migration|https://www.jetbrains.com/help/idea/type-migration.html] framework
> and adjusts it using custom structural-replace templates that express the
> adaptations required to perform the type changes.
> I want to apply several type changes using it and open the PR, thus
> introducing primitive functional interfaces in order to prevent unnecessary
> boxing (like BooleanSupplier instead Supplier<Boolean>, OptionalInt instead
> of Optional<Integer>, Predicate<T> instead of Function<T, Boolean>, etc. ),
> since it can affect the performance of the code (Effective Java, Items 44,
> 61).
> The patch itself is already prepared (because it is done automatically using
> the plugin), so I guess I will need to open this ticket, receive your
> approval, and then open the PR?
> It would help us a lot to evaluate the usefulness of our approach!
> Thank you in advance!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
